feat(ui): Apply LaunchDarkly Feature Flags to ABP MMDL and CHIP Eligibility Pages and Cards #1569
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Story: https://jiraent.cms.gov/browse/OY2-31722
Endpoint: https://d324rgo243013q.cloudfront.net/
Details
Wrapped the ABP MMDL and CHIP Eligibility cards in launch darkly flag:
mmdlNotification
so that when the flag is on, those options will not showImplementation Notes
mmdlNotification
flag rather than making my own flagTriage.js
so that if the flag is on, any card with the description containing MMDL will not showmmdlNotification
flag is on, the landing pages redirecting the MMDL will not be added (aka those routes will redirect to 'Not Found')Note: it seems my editor made some minor formating changes, I am sorry about that
Test Plan
mmdlNotification
flag offchoices/spa/medicaid
andchoices/spa/chip
still have the cards relating to MMDL