Skip to content

feat(ledger): reclassify a mapped account in place (replaces_association_id) - #252

Merged
jfrench9 merged 1 commit into
mainfrom
feature/reclassify-mapping
Oct 14, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
feature/reclassify-mapping

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

Regenerated against robosystems #1804 (reclassify a mapped account in place under the closed-period gate). Additive, generated tier: a client minor.

  • CreateMappingAssociationOperation gains replaces_association_id and reason; AssociationResponse gains replaced_association_id and reclassified_periods.
  • FactSetLite gains created_at (the month as closed on this date for a close-stamped set); schema.graphql refreshed to match.
  • The three mapping operations' descriptions follow the server's.

Waits on the server release carrying robosystems #1804 (the next after v1.16.17); nothing here calls a field the server does not already accept, so the client is safe to publish ahead of it.

Test plan

  • just generate-sdk + just generate-graphql from the local stack running #1804
  • just test (687 passed, 17 skipped)
  • just test-code

🤖 Generated with Claude Code

https://claude.ai/code/session_014Wxgk4yttBxgdE2uBHT71R

…ion_id)

Regenerated against robosystems #1804: replaces_association_id and
reason on create-mapping-association, replaced_association_id and
reclassified_periods on its response, created_at on FactSetLite, the
schema refreshed to match.

Claude-Session: https://claude.ai/code/session_014Wxgk4yttBxgdE2uBHT71R
@jfrench9
jfrench9 merged commit c9ba8fa into main Oct 14, 2026
4 checks passed
@jfrench9
jfrench9 deleted the feature/reclassify-mapping branch October 14, 2026 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant