fix(schemas): remove 'email' format for 'email' property in committer.schema.json #678
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
oscard0m
force-pushed
the
disable-format-for-email-in-commit-schema
branch
from
a609bd1 to
badef53
Compare
wolfy1339
approved these changes
Jul 21, 2022
|
🎉 This PR is included in version 6.2.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
format: emailfor"email"property incommitter.schema.jsonindex.jsonContext
emails aren't compliant with the RFC, not because of anything related to the JSON schema itself.
RFC 5322 Section 3.4 defines valid email addresses here: https://datatracker.ietf.org/doc/html/rfc5322#section-3.4
Example of not supported format:
41898282+github-actions[bot]@users.noreply.git.luolix.topFixes #453
Alternative solutions
To use the existing
patternfromajv-formatfor email and cover the use-case of emails. (#677)Discussion on-going in #453