Add better specification policy error description - #4658
Merged
deivid-rodriguez merged 2 commits intoJun 8, 2021
Merged
Conversation
ceritium
marked this pull request as ready for review
June 7, 2021 11:55
olleolleolle
approved these changes
Jun 7, 2021
olleolleolle
left a comment
olleolleolle
left a comment
Contributor
There was a problem hiding this comment.
I find this a useful developer experience improvement.
It would shorten the time it took for a user to correct their mistake.
simi
reviewed
Jun 7, 2021
deivid-rodriguez
added a commit
that referenced
this pull request
Jun 11, 2021
…rror-description Add better specification policy error description (cherry picked from commit 8eb1279)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
What was the end-user or developer problem that led to this PR?
Make easier find what key of metadata from
gemspecis invalid.What is your fix for the problem, implemented in this PR?
Print
metadata['#{key}']for string type and length value checks like for link keys.Make sure the following tasks are checked