selectCategoricalOption mutation for Phase 2 Store Refactor #366
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.
This PR closes #274 by implementing the following:
selectCategoricalOption
mutation in the store that takes a column name, option value and raw value and a) creates avalueMap
object ondataDictionary.annotated.<column_name>
if it does not exist, and b) assigns the raw value and option value as a key/value pair in thevalueMap
object.store-mutation-selectCategoricalOption.cy.js
that test a) if the value map is created when it does not yet exist, b) if the option (annotated) value is set in the value map for the raw value, and c) ensures a previously entered option value can be overwritten in the value map.annot-categorical
component and its component test inannot-categorical.cy.js
are updated to reflect changes for the newselectCategoricalOption
mutation