docs: document PathKey encoding and immer performance considerations (#14 #15) - #31
Merged
Conversation
…14 #15) - FormPath section: note JSON.stringify/parse could be replaced with NUL-separator encoding for large forms; benchmark before migrating - FormStateWriter section: note immer (~5KB) could be replaced with spread-based updates for flat record; benchmark before migrating - No code changes — design decision documentation Resolves #14 Resolves #15
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.
Summary
2개 P1 이슈를 문서화로 해결 (실제 최적화는 벤치마크 후 필요 시 진행).
Resolves #14
Resolves #15
Rationale
두 이슈 모두 성능 최적화 제안이지만 실제 벤치마크 없이는 추정에 불과. 현재 동작이 정확하고 가독성이 좋으므로, 설계 의사결정과 향후 최적화 경로를 문서화하여 해결.
Changes
#14 Path key JSON.stringify
JSON.stringify/JSON.parse를 NUL separator 인코딩으로 대체 가능하다는 점과 벤치마크 권고 추가#15 Immer runtime 의존성
Verification
Notes