Repository navigation
Move owned values when merging and flattening - #1530
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Consume owned vectors when merging request values and flattening dynamic components, avoiding clones of strings and nested JSON values. Scalar replacement, ordering, and error behavior are preserved.
Regression coverage reuses the existing dynamic-component parser test as a compact case matrix: object and string inputs, nested arrays, empty arrays, exact output order, and invalid properties. A seven-case SingleOrVec matrix covers scalar/array combinations and empty arrays without a separate setup harness. All prior assertions remain covered.
Validation: cargo fmt --all, cargo clippy --all-targets --all-features -- -D warnings, and cargo test --lib (236 tests passed).