test(store): add regression test for issue #303 draft nested array update - #304
Merged
Merged
Conversation
|
coverage: 99.957%. remained the same — agents/store-module-issue-303-investigation into main |
smalluban
force-pushed
the
agents/store-module-issue-303-investigation
branch
2 times, most recently
from
June 12, 2026 11:27
f095907 to
df97c86
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
smalluban
force-pushed
the
agents/store-module-issue-303-investigation
branch
from
June 16, 2026 07:45
df97c86 to
c2c2681
Compare
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.
This pull request references issue #303, where updating a draft enumerable model with a nested external array was reported to reset the array unexpectedly. To reproduce and guard this path, it adds a focused regression test in the store unit tests. The test now verifies that the first nested model is present before the update, then confirms that replacing it with a second nested model works as expected, documenting the reported sequence in executable form.