Repository navigation
Keep API-made stories editable after an observation (#408) - #162
Merged
Merged
Conversation
An observation copied project.updatedAt even when the story had none (stories created
through the API), leaving an undefined field that made every later edit fail the
plain-JSON check ('项目必须是普通 JSON 数据…'). Found on Codex's #408 fixture.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 22, 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
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.
Opening Codex's #408 fixture on staging showed the toast '项目必须是普通 JSON 数据…': the missing-file observation copied an absent
updatedAtasundefined, so all later edits failed validation (nothing was saved; fixture stayed at version 3). Fix + store regression test. Verified locally against staging: no toast, 9.0 s, fixture unchanged. npm test 871 pass.🤖 Generated with Claude Code