New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8277026: Remove blank lines remaining from snippet markup #6623
Conversation
|
@pavelrappo The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
* provided target. | ||
*/ | ||
record Link(String target) implements Style { } | ||
|
||
/** | ||
* A named style. Characters of this style are typically processed by | ||
* wrapping into an HTML {@code SPAN} element with the {@code class} | ||
* being wrapped into an HTML {@code SPAN} element with the {@code class} | ||
* attribute which is obtained from the provided name. | ||
*/ | ||
record Name(String name) implements Style { } | ||
|
||
/** | ||
* A marker of belonging to markup. Characters of this style are typically |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The initial sentence is a little awkward. Can it be rephrased to be clearer?
What is the significance of the use of "typically", at the end of the line. Are there cases where characters with this style are not omitted from the output?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you referring to this?
A named style.
Feel free to take a stab at it; I'm not good with words.
Nice.
I guess I was more expecting to filter output lines, rather than mark up input lines, but so far, I can't think of a problem case where they might be different. I have a couple of comments/questions about comment text, but no issues with the code. I look forward to using this in practice.
@pavelrappo This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 46 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
/integrate |
Going to push as commit da2be99.
Your commit was automatically rebased without conflicts. |
@pavelrappo Pushed as commit da2be99. |
This PR proposes to omit lines from the snippet source if those lines consist only of markup and perhaps whitespace. For example, if this PR is integrated, these three snippets will result in the same output:
While this change complicates the mental model for markup, it removes otherwise unavoidable inner blank lines in properties files, for example:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6623/head:pull/6623
$ git checkout pull/6623
Update a local copy of the PR:
$ git checkout pull/6623
$ git pull https://git.openjdk.java.net/jdk pull/6623/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6623
View PR using the GUI difftool:
$ git pr show -t 6623
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6623.diff