-
-
Notifications
You must be signed in to change notification settings - Fork 733
Do not allow spaces in external billing #13081
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
Do not allow spaces in external billing #13081
Conversation
dbb2515
to
39825a9
Compare
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.
Can you address the rubocop warning ?
@rioug I have requested the merge of the last master changes, and it seems that the Rubocop warning is gone, but now I have a test failing, it seems to be a flaky one. Do you know waht to do in this case? Can I trigger the checks without pushing a commit? |
On your fork you should be able to, but probably not in the OFN repo, but I can :) All good now, thanks ! |
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.
Looks good 👍
Hey @pacodelaluna , how are you 👋 |
Hi @sigmundpetersen, yes sorry, I was quite busy lately, I will take a look at this asap. |
baf8905
to
243d81c
Compare
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.
Thanks for updating the regexp, could you add test to make sure the regexp is doing what we want ?
@rioug I have added 2 tests for the new validation, please tell me if it is fine. |
Looks good, thanks for adding the test ! |
Hey @pacodelaluna , I've tested the superadmin field External Billing ID, and tried to introduce white spaces. Doing so, triggers this validation error: And does not change the previously introduced data, so that the ID remains without spaces. I've tested this for empty spaces in the:
Also tested removing the ID completely (deleting it), which is possible and works as before. Noticed though, that the report does not display none, as for other hubs, after a previously saved ID is deleted (notice the empty space on the column below): This is not introduced by this PR. So, with the validation you've introduced, we can be sure that the ID does not have empty spaces 🎉 Merging. |
What? Why?
I forgot to add a basic validation on the external_billing_id field on my last PR.
What should we test?
Release notes
Changelog Category (reviewers may add a label for the release notes):