Update required-fields plugin
#7
Merged
Conversation
This file contains hidden or 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
With this change, the plugin now also validates the name of the fields against a set of preferred field names. For instance, the linting will fail if you try to define a field named `updated_at` and will recommend you to use `last_modified_at`. At this moment I considered it isn't worth to add this functionality as a new plugin, in the future we could either rename the plugin or split the functionality.
areina
force-pushed
the
feat/toni/preferred-field-names
branch
from
14990b4 to
5208ef1
Compare
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.
With this change, the plugin now also validates the name of the fields against a set of preferred field names. For instance, the linting will fail if you try to define a field named
updated_atand will recommend you to uselast_modified_at.Example:
At this moment I considered it isn't worth to add this functionality as a new plugin, in the future we could either rename the plugin or split the functionality.