-
Notifications
You must be signed in to change notification settings - Fork 45
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
23604 update logic for changing business name #599
23604 update logic for changing business name #599
Conversation
@@ -433,24 +433,20 @@ export default class ChangeBusinessType extends Mixins(CommonMixin) { | |||
submitTypeChange () { | |||
this.setEntityType(this.selectedEntityType) | |||
this.isEditingType = false | |||
if (this.shouldUpdateName()) { |
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.
Using the old logic, we would only update the name and set the NR if the business name had NOT changed. This prevents the case when a user attempts to change the business type (and therefore the name) more than once, as the business name HAS changed in this case.
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.
Does this logic work on a named company? With and without a new NR?
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.
Since these changes still retain the check for a numbered business, as before, named companies should not be reaching this block of code below. There should be separate logic that handles named businesses (I can verify where this is if you like).
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.
Please verify and/or test if you haven't already.
I did a little test on a named BC Limited, and could not change the type to ULC without a NR.
As before, I could not change a named BC to a numbered ULC in one step -- it would take one alteration to change it to numbered, and a second one to change the type. But that's a future ticket so don't worry about it.
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.
I did a little test on a named BC Limited, and could not change the type to ULC without a NR.
I thought this was the expected behaviour for named businesses? Since altering the business type for a named business would require a name change and this requires an NR.
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.
Yes, but what if wanted to change my named BC to a numbered ULC? Anyway, we discussed this previously and decided it was low priority right now.
/gcbrun |
Temporary Url for review: https://business-edit-dev--pr-599-h6gsnubn.web.app Test with: https://business-edit-dev--pr-599-h6gsnubn.web.app/BC0883760/alteration?accountid=3627 |
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.
Good analysis and I agree with the solution, but please test a bit more (including saving and resuming) to make sure all edge cases are OK, too. Thanks!
I did some tests, seems good! |
/gcbrun |
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.
I did some quick tests and it LGTM!
Please list out, in the ticket, the tests you did. Great job! Thanks!
Issue #: /bcgov/entity#23604
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 bcrs-entities-create-ui license (Apache 2.0).