-
Notifications
You must be signed in to change notification settings - Fork 84
32958 Business Emailer - updates for reg and cor #4542
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
Open
kialj876
wants to merge
7
commits into
bcgov:main
Choose a base branch
from
kialj876:32958-email-update-reg-cor
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+639
−1,231
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
de4a7ea
32958 Business Emailer - updates for reg and cor
kialj876 203b367
chore: cleanup sonarqube
kialj876 63c47ca
Address PR comment
kialj876 7c66889
update get_recipients to address pr comments
kialj876 d6ec068
chore: lint and sonarqube
kialj876 baf8121
Adjust unit test bootstrap filings setup
kialj876 427a968
chore: sonarqube
kialj876 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
183 changes: 0 additions & 183 deletions
183
...ness-emailer/src/business_emailer/email_processors/change_of_registration_notification.py
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
get_recipients reads filing_json["filing"]["business"]["identifier"] directly (line 66), but new business filings like incorporation and registration don't have a business block yet (your own prep_registration_filing deletes it for PAID), so this'll throw a KeyError on something like a future-effective incorporation
can we guard it with .get("business", {})?
Uh oh!
There was an error while loading. Please reload this page.
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.
This is actually required by the schema so it will always be there. In the case of a bootstrap filing (incorp/amalg/cont in/registration) this would be a temporary identifier (regardless if its future effective or not). I will update the tests so that its realistic / more clear
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.
Okay I adjusted a couple things to make it more clear about the temp reg and made the tests setup more realistic