Add Trip Editor rich-notes persistence contracts#302
Merged
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
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.
Summary
Implements #297 Batch 5 only: Trip Editor request-boundary rich-notes normalization and persistence coverage.
EditorRichNotesRequestHtmlas a Trip Editor request-boundary helper, not a broad app sanitizer.Claim Boundary
Existing rich-notes Playwright specs remain mocked/fixture-backed and validate editor UX, client canonicalization, request shape, image-dialog behavior, and draft behavior only. They are not backend persistence proof.
The real persistence proof in this PR is limited to the new metadata rich-notes persistence spec plus backend request-boundary tests for the shared parser path.
Out Of Scope
Validation
dotnet buildpassed.dotnet testpassed, 1547 tests.git diff --check origin/main...HEADpassed.