feat(projects): expose startOn on create_project and update_project#88
Merged
Conversation
startOn was always present on project responses but never settable through the connector. Wire-verified before implementing (ZZZ probe, cleaned up): POST /kases with startOn -> 201 with the value stored and echoed; PUT startOn -> 200; PUT startOn: null -> 200 with the field cleared. create_project takes an optional YYYY-MM-DD startOn; update_project takes nullable+optional with the connector's usual date semantics (undefined = leave untouched, null = clear). Both handlers already spread rest fields into the wire body, so the schema addition is the whole change. Tests +3 (create forwards it; update sets and null-clears; schema rejects non-date strings). 579 pass; typecheck + biome + build green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Fixes the first of the two reported connector gaps:
startOncouldn't be set through the connector — it was always present on project responses but absent from both write schemas.Wire-verified before implementing (live ZZZ probe, cleaned up):
POST /kaseswithstartOn→ 201 stored+echoed;PUTchange → 200;PUT startOn: null→ 200 cleared.create_project: optionalstartOn(YYYY-MM-DD)update_project: nullable+optional, matching the connector's date semantics (undefined= leave untouched,null= clear)Tests +3. 579 pass; typecheck + biome + build green.
🤖 Generated with Claude Code