Add coercion/normalization of Choice values
See original GitHub issueI want my CLI to be case insensitive for certain Choice
options but I don’t want to deal with that variability internally as it has no meaning. I think an option like coerce_case
or normalize_case
would be a reasonable addition.
PR to follow.
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Normalization Rules - Cerberus
Value Coercion Coercion allows you to apply a callable (given as object or the name of a custom coercion method) to a...
Read more >GVV Pillar 3: Normalization - Ethics Unwrapped
Normalization means expecting values conflicts so that you approach them calmly and competently. Over-reaction can limit your choices unnecessarily.
Read more >coerce | Elasticsearch Guide [8.5] | Elastic
Coercion attempts to clean up dirty values to fit the data type of a field. For instance: Strings will be coerced to numbers....
Read more >RnBeads source: R/normalization.R - Rdrr.io
R/normalization.R defines the following functions: rnb.step.imputation rnb.section.imputation rnb.execute.imputation median.imputation knn.imputation ...
Read more >Create ETL entity field definitions - ServiceNow Docs
Coercion action, What the system should do if a reference or choice could not be ... The ignore option sets the current value...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Seems fine for 7.1, along with clarifying the documentation of the option, it would be good to add an example of normalizing to lowercase if there’s not one already.
#1318 merged so the issue should be resolved.