You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The CSV card import description is ambiguous. The mentioned column format does not inform the user whether the column is actually required or optional.
Describe the solution you'd like
It should be clear what columns are required and which are optional.
This can be done by either:
marking required columns with an asterisk (*)
marking optional columns with an (optional)
adding a separate bullet point Optionale Spalten or similar
Refactoring the card config to avoid having three separate config arrays (i.e. extensionColumnNames, extensions, extensionRequirement). Instead, we could do something like:
Is your feature request related to a problem? Please describe.
The CSV card import description is ambiguous. The mentioned column format does not inform the user whether the column is actually required or optional.
Describe the solution you'd like
It should be clear what columns are required and which are optional.
This can be done by either:
(*)
(optional)
Optionale Spalten
or similarRefactoring the card config to avoid having three separate config arrays (i.e. extensionColumnNames, extensions, extensionRequirement). Instead, we could do something like:
Describe alternatives you've considered
Leave it as it is.
Additional context
This was brought up here: #1715 (review)
The text was updated successfully, but these errors were encountered: