Skip to content
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

Merged
merged 19 commits into from
Jul 6, 2021

Conversation

rocketnova
Copy link
Contributor

@rocketnova rocketnova commented Jun 29, 2021

Ticket

Related to #242

Changes

  • Splits the Base State scenarios into the current 4 known scenarios (more refinement TBD)
  • Updates scenarios to be numbered
  • Converts scenario type enum from an enum with string members to an enum with number members
  • Adds a type alias for i18n translation strings so that we can use the type I18nString instead of just string for extra clarity

Context

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

@rocketnova rocketnova added Engineering Technology and Development Track and removed Engineering Technology and Development Track labels Jun 29, 2021
utils/getScenarioContent.tsx Outdated Show resolved Hide resolved
@rocketnova rocketnova marked this pull request as draft July 2, 2021 02:48
stories/Page.stories.tsx Show resolved Hide resolved
tests/utils/apiGatewayStub.test.tsx Show resolved Hide resolved
tests/utils/getScenarioContent.test.tsx Show resolved Hide resolved
utils/getScenarioContent.tsx Show resolved Hide resolved
else {
// throw new Error('Unexpected scenario')
Copy link
Contributor Author

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.

@rocketnova rocketnova marked this pull request as ready for review July 2, 2021 02:56
utils/getScenarioContent.tsx Outdated Show resolved Hide resolved
tests/utils/apiGatewayStub.test.tsx Show resolved Hide resolved
utils/getScenarioContent.tsx Show resolved Hide resolved
Copy link
Contributor

@lomky lomky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@rocketnova rocketnova merged commit 16c3ee3 into main Jul 6, 2021
@rocketnova rocketnova deleted the rocket/242-split-scenario branch July 6, 2021 21:35
This was referenced Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants