Configurable regex for description #52
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.
Current problem
The description must follow an hardcoded regular expression :
^[a-zA-Z0-9\s]+$. This does not allow players to use their language. Neither accents nor special characters are allowed, and it is impossible to add colours, although this is technically allowed.Solution
Because the database already stores the description as a
VARCHAR(255), there is no reason to restrict the server admin to an alphanumerical string for all player claims. As such, we can simply add a configuration entry to specify a regex that should be allowed for players.Features :
description-regex.claimsanddescription-regex.protected-areas. As the name implies, each one of them defines a pattern the in-game users will have to follow.§andChatColor, the simplest way of doing so is withChatColor.translateAlternateColorCodes.lang/directory.