-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Fyst-294] add notification preferences page #5027
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
Heroku app: https://gyr-review-app-5027-815e197df5c3.herokuapp.com/ |
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
Co-authored-by: Mike Rotondo <[email protected]>
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 think you are missing form specs at least. The form is pretty simple so I think you can get away with a quick one with just shoulda_matchers
. The controller is so basic as to more or less not be there so I guess it's alright to not have a spec.
Co-authored-by: Mike Rotondo <[email protected]>
Good call, added form specs for the validations |
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! You may consider using shoulda_matchers
in the future which can simplify standard rails tests. Not that it's invalid to do things this way, I just personally find writing validator tests a little tedious lol
fb1ac42
to
c7aeb80
Compare
Co-authored-by: Tahsina Islam <[email protected]> Co-authored-by: Anisha Ramnani <[email protected]>
* tweak the default render call for landing page bullets * hint for the linter; because the key is used as a default, the i18n linter doesn't recognize it as being used Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
Adds persona import/export CLI tool Co-authored-by: Hugo Melo <[email protected]>
* johnny * alexis * shell Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
Co-authored-by: Hugo Melo <[email protected]>
3b2446e
to
a247a94
Compare
Co-authored-by: Hugo Melo <[email protected]>
Link to pivotal/JIRA issue
https://codeforamerica.atlassian.net/browse/FYST-294
Is PM acceptance required? (delete one)
Reminder: merge main into this branch and get green tests before merging to main
What was done?
Add
:sms_notification_opt_in
and:email_notification_opt_in
How to test?
Step through state return flows until you've verified a code, then enter either a phone number or select email
Screenshot