Skip to content

docs(spec): clarify has index guard - #25284

Closed
mig-builds wants to merge 1 commit into
objectstack-ai:mainfrom
mig-builds:contrib/issue-25282-clarify-has-index-guard
Closed

mig-builds wants to merge 1 commit into
objectstack-ai:mainfrom
mig-builds:contrib/issue-25282-clarify-has-index-guard

Conversation

@mig-builds

Copy link
Copy Markdown
Contributor

Fixes #25282

Clarifies that terminal indexes are refused by has(), while intermediate numeric segments remain unguarded because the guard builder emits named field selections only.

Validation:

  • pnpm --filter @objectstack/spec build
  • pnpm --filter @objectstack/spec check:generated
  • pnpm --filter @objectstack/spec test -- flow-value-slot-template.test.ts

@objectstack-fleet

Copy link
Copy Markdown
Contributor

Thank you, @mig-builds, for this fix and for the clear validation steps.

Both this PR and #25367 state the post-#25275 has() rule correctly. The maintainer chose to land #25367 (ruling 6358845679 on #25282, letter A), because it also gives the exact reason such a path gets no guard: a step-at-a-time guard would end one has() on the index, and has() refuses an index as its last step. This repository lands contributions through an internal branch (card-first), so I'm closing this one in favour of #25367. Its landing commit carries Co-authored-by: mig-builds <54319294+mig-builds@users.noreply.github.com> to credit your work.

Thanks again. Contributions like this are very welcome.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant