Fix Kotlin code formatting for Inline Maps section of ref docs #26836
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
spring-projects-issues
added
the
status: waiting-for-triage
|
I see that validation failed because of some internal error. Please check it. |
In the future, please provide a link to the affected section of the reference manual, since the page numbers of the PDF can change -- for example, "in the Inline Maps section". If you don't want to provide a link, stating something like "in the Inline Maps section of the SpEL chapter" is also sufficient. Thanks |
sbrannen
added
type: task
sbrannen
changed the title
|
This has been merged into Thanks |
lxbzmy
pushed a commit
to lxbzmy/spring-framework
that referenced
this pull request
Mar 26, 2022
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.
Official documentation contains incorrect Kotlin code example (page 292 of pdf).
There are
Map<*, >instead ofMap<*, *>andMap<, *>instead ofMap<*, *>.The cause of this issue is incorrect formatting.