feat: поддержка RFC 6901 (JSON Pointer) для путей — escaping ~/slash в ключах (Этап 10.2, Issue #206)#223
Merged
Conversation
Adding .gitkeep for PR creation (default mode). This file will be removed when the task is complete. Issue: netkeep80#206
…в ключах (Этап 10.2, Issue netkeep80#206) Добавлена функция pjson_decode_rfc6901_segment() для декодирования сегментов пути по RFC 6901: ~1 → /, ~0 → ~. Декодирование применяется в _walk_path() и pjson_split_path(). Ключи объектов, содержащие '/' и '~', теперь доступны через path-адресацию с экранированием. Добавлены 17 тестов. Все 676 тестов проходят. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
konard
changed the title
This reverts commit 61977e4.
Contributor
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Gist (1316KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
Contributor
Author
🔄 Auto-restart triggered (iteration 1)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. Will continue until PR becomes mergeable. |
…ompatibility On Windows/MSVC, CTest corrupts Unicode characters (em dash '—' becomes garbled 'ΓÇö') when passing test names to the Catch2 binary, causing all 8 decode segment tests to fail with "No test cases matched". Replace em dash with ASCII hyphen-minus in TEST_CASE names. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
🔄 Auto-restart-until-mergeable Log (iteration 1)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Gist (2214KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
Contributor
Author
✅ Ready to mergeThis pull request is now ready to be merged:
Monitored by hive-mind with --auto-restart-until-mergeable flag |
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
pjson_decode_rfc6901_segment()вpjson_db_helpers.hдля декодирования сегментов пути по RFC 6901:~1→/,~0→~_walk_path()вpjson_db_pmm.hдекодирует каждый сегмент пути через RFC 6901pjson_split_path()вpjson_db_helpers.hдекодирует последний сегмент через RFC 6901tests/test_pjson_rfc6901.cppplan.mdиreadme.mdКонтекст
Это Этап 10.2 (Проблема 7) из plan.md. Ранее ключи объектов, содержащие
/, были недоступны через path-адресацию. Теперь поддерживается экранирование по RFC 6901 (JSON Pointer):~→~0,/→~1.Пример:
Fixes
Fixes #206
Test plan
deps/pmm/pmm.h)🤖 Generated with Claude Code