You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cd40a92
Browse filesBrowse the repository at this point in the historyBrowse files
Format MOE strip markers in javadoc like any other HTML comment
google/MOE, the tool whose intracomment-strip markers the javadoc formatter
recognised, has been dead for years. The lexer no longer gives
`<!-- MOE:begin_intracomment_strip -->` and `<!-- MOE:end_intracomment_strip -->`
token types of their own, and the writer loses the state that queued the begin
marker until the next token and remembered its indent for the end marker: both
markers now take the HTML comment path, a line of their own at the indent of
the text around them.
The layouts the old test pinned change in two places: a blank line the next
tag asks for comes after the begin marker instead of before it, and a marker
inside or between footer tags is indented as a continuation line of the tag it
follows. A begin marker that closes the comment without an end marker is kept
instead of silently deleted.
The test was written first: moeStripMarkersAreOrdinaryHtmlComments failed
before the change; the three cases that only guarded the begin/end pairing
against exploding are gone. None of the 15,747 JDK 21 sources changes with
javadoc formatting on; the JDK carries no MOE markers.
0 commit comments