Allow everything but unicode emojis #1178
Merged
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.
Description
We previously disallowed a lot of characters from specific fields and decided to go with basically the same thing for the project description. However, the Order Portal allows for all characters, and those using this often collect the order information and use this when creating the data delivery project. This causes the DDS to refuse the project because the description for example contains "invalid characters".
When looking at this I at first couldn't find what had been producing the errors before, but finally I realised that it's unicode characters and emojis that product SQLAlchemyErrors. In this PR I have changed the description validation to allow all characters except the unicode emojis/signs/characters etc.
Fixes DDS-1293
Type of change
Checklist:
Please delete options that are not relevant.
Formatting and documentation
Tests