🐛 fix(import): preserve @meta: keys during JSON chunking#51
Merged
david-vaclavek merged 1 commit intomainfrom Mar 26, 2026
Merged
🐛 fix(import): preserve @meta: keys during JSON chunking#51david-vaclavek merged 1 commit intomainfrom
david-vaclavek merged 1 commit intomainfrom
Conversation
`sliceByValue` was recursing into `@meta:` entry values (e.g.
`{ "limit": 80 }`) because they are plain objects. This caused the
`@meta:` key to be split on dots during path reconstruction with
`setWith`, destroying the flat key structure and making the server
unable to match metadata to content keys.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
honzabubenik
approved these changes
Mar 26, 2026
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
@meta:entries with object values (e.g.{ "limit": 80 }) were being recursed into bysliceByValue, causing the@meta:key to be split on dots during path reconstruction with lodashsetWith@meta:keys were silently lost when the key contained dots (e.g. Strapi-style keys likeapi::article.article[doc1].description)!key.startsWith('@meta:')check to treat@meta:entries as leaf values instead of recursing into themTest plan
@meta:entries containing dotted keys and verify limits are preserved@meta:entries🤖 Generated with Claude Code