Conversation
…ersion Audit entries on the same day were incorrectly merged into one group even when a labelled version sat between them. Now grouping only applies to consecutive audits with no version boundary in between. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
Commits
|
chrischrischris
approved these changes
May 13, 2026
This was referenced May 15, 2026
chrischrischris
added a commit
that referenced
this pull request
May 15, 2026
…939) PR #931 changed formatVersions to keep audit entries in separate groups when split by a labeled version boundary. The test now finds two .is-audit elements (one before and one after 'ver 1'), causing a strict mode violation. Use .first() to target the most recent audit group. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 participants
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
When two audit entries fell on the same calendar day but were separated by a labelled version, they were incorrectly merged into a single group — breaking the chronological block structure of the history panel.
Test plan
Before:
After
Open the version history and check the May 5th ordering:
before: Previewed, all edit sessions, rest of the Previewed
now: edit session then Previewed, edit session then Previewed....
Open the version history panel for a document that has audit entries both before and after a labelled version on the same day — verify they appear in two separate groups with the labelled version between them
Verify that consecutive audit entries on the same day (with no version in between) are still grouped together as before
npm testpasses🤖 Generated with Claude Code