-
Notifications
You must be signed in to change notification settings - Fork 4
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
Split scenario "base state (no pending weeks)" into two sub scenarios #266
Conversation
else { | ||
// throw new Error('Unexpected scenario') |
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.
Note: The new logic I went over with Nicole and Diana shouldn't leave an opportunity for an unknown scenario. We will also have an additional layer of API gateway response validation (#150) that will make unexpected response values not possible.
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.
🎉
Ticket
Related to #242
Changes
I18nString
instead of juststring
for extra clarityContext
While going through the content matrix, I discovered that I didn't break out the scenarios at the correct level of granularity in order to display the content we want to show. After getting confirmation about this from @nicoleslaw and Diana, this PR corrects that.
Testing
yarn test