-
Notifications
You must be signed in to change notification settings - Fork 237
Add preceding newlines before Doxygen commands #237
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
Open
a7medev
wants to merge
2
commits into
swiftlang:main
Choose a base branch
from
a7medev:fix/newline-before-doxygen
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1626,4 +1626,58 @@ class MarkupFormatterMixedContentTests: XCTestCase { | |
] | ||
zip(expected, printed).forEach { XCTAssertEqual($0, $1) } | ||
} | ||
|
||
func testDoxygenCommandsPrecedingNewlinesWithSingleNewline() { | ||
let expected = #""" | ||
Does something. | ||
|
||
\abstract abstract | ||
\param x first param | ||
\returns result | ||
\note note | ||
\discussion discussion | ||
"""# | ||
|
||
let formattingOptions = MarkupFormatter.Options( | ||
adjacentDoxygenCommandsSpacing: .singleNewline) | ||
let printed = Document( | ||
Paragraph(Text("Does something.")), | ||
DoxygenAbstract(children: Paragraph(Text("abstract"))), | ||
DoxygenParameter(name: "x", children: Paragraph(Text("first param"))), | ||
DoxygenReturns(children: Paragraph(Text("result"))), | ||
DoxygenNote(children: Paragraph(Text("note"))), | ||
DoxygenDiscussion(children: Paragraph(Text("discussion"))) | ||
).format(options: formattingOptions) | ||
|
||
XCTAssertEqual(expected, printed) | ||
} | ||
|
||
func testDoxygenCommandsPrecedingNewlinesAsSeparateParagraphs() { | ||
let expected = #""" | ||
Does something. | ||
|
||
\abstract abstract | ||
|
||
\param x first param | ||
|
||
\returns result | ||
|
||
\note note | ||
|
||
\discussion discussion | ||
"""# | ||
|
||
let formattingOptions = MarkupFormatter.Options( | ||
adjacentDoxygenCommandsSpacing: .separateParagraphs) | ||
let printed = Document( | ||
Paragraph(Text("Does something.")), | ||
DoxygenAbstract(children: Paragraph(Text("abstract"))), | ||
DoxygenParameter(name: "x", children: Paragraph(Text("first param"))), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How would this behave with two different parameters? I wouldn't expect that to have blank lines in-between. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same reasoning as above. |
||
DoxygenReturns(children: Paragraph(Text("result"))), | ||
DoxygenNote(children: Paragraph(Text("note"))), | ||
DoxygenDiscussion(children: Paragraph(Text("discussion"))) | ||
).format(options: formattingOptions) | ||
|
||
XCTAssertEqual(expected, printed) | ||
} | ||
} |
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.
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.
Do these need a blank line in between or would they parse the same if they were just on their own line (without blank lines in between)?
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.
They'd parse the same without a blank line.
A non-Doxygen-aware markdown renderer would show them on the same line without the blank line though (and most LSP clients like VS Code aren't Doxygen-aware).
If you don't think this is something swift-markdown needs to handle, would it be okay to add an option to always add a blank between Doxygen commands? If not, what do you recommend?
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.
From what i've been able to see, Doxygen commands (and HeaderDoc tags, which are similar) are usually written without an interleaving newline between commands, especially commands of the same kind like
\param
. Comparing this behavior "when parsed by a non-Doxygen-aware parser" doesn't seem that important to me, since Doxygen commands are non-standard Markdown to begin with.I would much rather prefer to see "preceding newlines" as a configurable option, with 1 newline (i.e. without an interleaving blank line) as the default. (Maybe as a toggle, something like "print Doxygen commands as separate paragraphs", where turning it on has the behavior you've written, and leaving it off only prints one newline.) You did find a valuable bug in that we don't print any newlines for Doxygen commands at all, so i would want to make sure that we at least print them correctly.
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.
@QuietMisdreavus @d-ronnqvist That makes sense. I updated the implementation to control this behavior with an option. Please recheck. 🙏🏼