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
The option DOT_OR_USCORE has not been tested for almost a year, due to a change in UFS_UTILS that forces underscores in filenames. Since it is no longer relevant, this option should be deprecated/removed from SRW.
Solution
Remove this option from SRW. If the files in question may have different naming conventions in the future or for some other application, then the whole filename should be configurable, not just some weird switch for punctuation. Especially with the more modern ability to use jinja substitution, there shouldn't be any reason why such a switch is needed.
Requirements**
Remove all references to DOT_OR_USCORE, replace with a literal underscore where appropriate in filenames.
Acceptance Criteria (Definition of Done)
See requirements.
Dependencies (optional)
None known
Alternative Solutions (optional)
Continue to leave this dangling relic in the workflow. Not ideal.
The text was updated successfully, but these errors were encountered:
Description
The option
DOT_OR_USCORE
has not been tested for almost a year, due to a change in UFS_UTILS that forces underscores in filenames. Since it is no longer relevant, this option should be deprecated/removed from SRW.Solution
Remove this option from SRW. If the files in question may have different naming conventions in the future or for some other application, then the whole filename should be configurable, not just some weird switch for punctuation. Especially with the more modern ability to use jinja substitution, there shouldn't be any reason why such a switch is needed.
Requirements**
Remove all references to
DOT_OR_USCORE
, replace with a literal underscore where appropriate in filenames.Acceptance Criteria (Definition of Done)
See requirements.
Dependencies (optional)
None known
Alternative Solutions (optional)
Continue to leave this dangling relic in the workflow. Not ideal.
The text was updated successfully, but these errors were encountered: