Docs: explain breaking long lines in Groovy#70
Open
Gitkbc wants to merge 1 commit into
Open
Conversation
Contributor
|
Thanks for looking into this. There are no doubt many places where the doco can be improved. Most of the documentation that might change between Groovy versions is kept in the groovy repo itself not this one. Perhaps style-guide.adoc and/or core-syntax.adoc and/or core-differences-java.adoc in that repo might be better places to consider changes. For long strings, Groovy's various multi-line strings and related method calls are generally preferred to concatenated strings. I would also expect to see some discussion about repeated method calls and expressions with operators. |
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
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.
Fixes #64
This PR enhances the Groovy documentation by adding guidance on how to
break long lines into multiple lines, which is helpful when addressing
linter warnings such as LineLength.
The documentation includes a clear example showing how collections can
span multiple lines, improving readability and maintainability.
If this content would be better placed in an existing documentation
section or requires adjustment to match project conventions, I’m happy
to update it based on maintainer feedback.