Uh oh!
There was an error while loading. Please reload this page.
docs: drop refused dotted-fields remedy from v17 release notes - #8393
Merged
Conversation
The v17.mdx removed-features row for the fields[] object form prescribed a dotted path (fields: ['owner.name']) as a fallback alongside expand. That spelling is now refused at both doors (REST ingress since #7532/PR #7588, engine find/findOne since #7589/PR #8327), so the remedy pointed upgraders straight into the refusal it was meant to route around. Per the card's own prescription: drop the dotted alternative, keep expand alone with the reference column preserved in the projection. Fixes#8329 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jqe56GnYFddggeAyfkZFVz
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
qq9340100
marked this pull request as ready for review
August 13, 2026 11:17
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Fixes#8329
Sanctioned shape
This is the dedicated docs-only PR for a
content/docs/releases/factual error, per the release-notes guardrail (AGENTS.md / CLAUDE.md): release pages are release-owned and read-only in a code PR, so this correction lands as its own PR rather than a rider on any code change. Nothing outside the one table cell below is touched, and this PR carries no changeset (docs-only,skip-changesetapplied — see below).What changed
content/docs/releases/v17.mdxline 977, the removed-features row for the retiredfields[]object form{ field, fields, alias }, prescribed in its "Use instead" column:The dotted-path half of that remedy is now refused at both doors:
400 INVALID_FIELDat the REST ingress (PR #7588) and on directengine.find/engine.findOnecalls (PR #8327). Following the published remedy would land an upgrader in the exact refusal it was meant to route around.Per the card's own prescription (already triaged as settled), the cell now reads:
The dotted alternative is dropped, not reworded — the relation is carried by the projected column, so removing that column would leave
expandnothing to resolve.Verification
pnpm check:docs-audit-scope— passpnpm check:quick-reference-counts— passpnpm check:release-notes— passpnpm check:role-word— passpnpm --filter @objectstack/lint run check:doc-formula-expressions— pass (required buildingpackages/formula's dist first viapnpm --filter '@objectstack/lint^...' buildin this fresh worktree)pnpm check:nul-bytes— passnode scripts/pm/dispatch-gates.mjs content/docs/releases/v17.mdx— surfaced exactly the five gates above, no additions.Generated by Claude Code
Generated by Claude Code