Plugin Directory: Allow 'for-X-and-TRADEMARK' pattern in plugin names #537
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.
This update extends the trademark validation logic to support plugin names following the pattern "for-{service}-and-{trademark}", in addition to the existing "for-{trademark}" pattern.
This allows more natural plugin naming for integrations that connect multiple services, while still maintaining trademark protection requirements.
Examples of now-allowed names:
The following patterns remain blocked (as expected):
All existing trademark validations remain intact and functional.