-
Notifications
You must be signed in to change notification settings - Fork 0
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
Custom value mapping for Boolean attributes #43
Comments
Jumas
added a commit
to SchweizerischeBundesbahnen/ch.sbb.polarion.extension.generic
that referenced
this issue
Oct 2, 2024
Merged
4 tasks
Jumas
added a commit
to SchweizerischeBundesbahnen/ch.sbb.polarion.extension.generic
that referenced
this issue
Oct 2, 2024
Jumas
added a commit
that referenced
this issue
Oct 3, 2024
4 tasks
4 tasks
Jumas
added a commit
that referenced
this issue
Oct 3, 2024
4 tasks
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
For Boolean attributes, implement the option to map specific input values to true/false in the mapping configuration (e.g. that "yes" is mapped to "true"). This kind of custom mapping is already possible for Enum values but not Boolean. The UI should be similar to the custom Enum mapping UI.
In v2.8.0, if a value is imported that doesn't match any of the configured mapping options, it will be treated as if it was mapped to false. Instead, the import should be unsuccessful and result in an error with an appropriate error message. This way, it makes it harder to accidentally import typos and is also consistent with how custom Enum mapping works.
Motivation
Users of Excel Importer might be working with Excel files that contain other Boolean values than true/false, such as yes/no or X/(empty). Instead of having to correct every differing Boolean value in the file, it would be simpler if they could just configure the mapping, like they already do with Enum values.
Proposed Solution (optional)
The custom Boolean mapping could be implemented similar to the current implementation of custom Enum mapping.
The text was updated successfully, but these errors were encountered: