Repository navigation
Conversation
This branch has not been deployed
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
1 participant
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.
Issue
fixes #600
LLM Use
an LLM reviewed my code, i didn't apply any of its suggestions
Description
parsePrelude()now also returns where the last empty line between comments was. when the prelude doesn't end with an empty line, the part before that point goes todoc.commentBeforeand the rest to the value, so#foo\n\n#bar\n42gives'foo'on the document and'bar'on the value. stringified output doesn't change.seq comments without #expected the combined' c1\n\n c2'on the first item, updated it to' c1'on the document and' c2'on the item.