No space after keywords #585
Merged
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
WebFreak001
requested changes
Jul 26, 2023
There was a problem hiding this comment.
can you add a test case? Go into the tests folder, create a file like space_after_keywords.d with the various keyword statements described here (if, while, foreach, for, with), then run
echo '--space_after_keywords=false' > space_after_keywords.args
./gen_expected.sh space_after_keywords
confirm that the formatting is like what you expect and add it to this PR
Readme update test files
58adc10 to
edd40b8
Compare
|
done |
WebFreak001
approved these changes
Jul 26, 2023
The generator is so outdated and basic that it didn't generate this.
|
awesome, thank you |
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.
No more spaces after keywords like if,foreach,while,for, etc.