Specs 02, 14, and 15a: Fix Style #62
Open
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
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.
Because
Style issues found by Rubocop version 1.66.1
This PR
Noteshould be all upper case, followed by a colon, and a space, then a note describing the problem.RuboCopStyle/CommentAnnotation"Issue
Additional Information
Pull Request Requirements
location of change: brief description of changeformat, e.g.String spec: Update instructions for clarityBecausesection summarizes the reason for this PRThis PRsection has a bullet point list describing the changes in this PRIssuesectionspecfolder, they are also updated in the corresponding file in thespec_answersfolder (with passing tests).