-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
21476 update good standing logic to include transition filing criteria #2756
21476 update good standing logic to include transition filing criteria #2756
Conversation
…flag 'enable_involuntary_dissolution' is on)
Quality Gate passedIssues Measures |
…format the code in tests
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2756 +/- ##
==========================================
+ Coverage 75.49% 76.77% +1.28%
==========================================
Files 196 177 -19
Lines 12264 11257 -1007
Branches 2054 1931 -123
==========================================
- Hits 9259 8643 -616
+ Misses 2442 2103 -339
+ Partials 563 511 -52
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except for the issues mentioned by hongjing, everything else is fine for me.
they are all addressed now 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐱
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All changes look good to me.
Issue #: /bcgov/entity#21476
Description of changes:
Implemented the logic to include transition filing logic used in involuntary dissolution eligibility check in
business.good_standing
.(
enable_involuntary_dissolution
feature flag)The main logic is same as the
_has_no_transition_filed_after_restoration()
method in involuntary dissolution.Differences are:
.scalar()
after the query.Also added unit tests to check 4 situations:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the lear license (Apache 2.0).