-
Notifications
You must be signed in to change notification settings - Fork 71
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
19343 Add not in good standing blocker to amalgamations #2402
Conversation
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2402 +/- ##
==========================================
- Coverage 77.37% 76.62% -0.76%
==========================================
Files 202 168 -34
Lines 11602 10548 -1054
Branches 1961 1794 -167
==========================================
- Hits 8977 8082 -895
+ Misses 2043 1978 -65
+ Partials 582 488 -94
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@leodube-aot can you verify with Mihai if a not in good standing check is really ok? Not in good standing will cover a business in limited restoration but there are other conditions where a business is not in good standing. Should all the other scenarios where a business is not in good standing block starting an amalgamation filing from a TING? |
@argush3 Sure thing, I'll ask Mihai and update here. Edit: We are blocking all not in good standing scenarios. |
Issue #: /bcgov/entity#19343
Description of changes:
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).