Repository navigation
feat(server): write a source's link parameters into the page's query string - #640
Merged
Merged
Conversation
…string create_link takes the parameters a source lists in sources.<id>.linkParams and writes their checked values into the query string of the source's page. The view stays in the fragment. Any other parameter answers INVALID_INPUT and names the allowed ones; a claim-bound one never goes into a link. A query the page address holds stays. GET /sources and list_sources name the list, check-config prints it. Record 0016 is accepted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… applies the query rules Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, the REST texts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.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
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 #619
create_linkwrites a source's parameters into the page's query string, such as?customer=acme. The view stays in the fragment. A host application's backend can read the query. Record 0016 is set to accepted.What changes
sources.<id>.linkParamslists the parameters a link may carry, per source. The values go into the query string ofsources.<id>.link.create_link(MCP andPOST /views/link) refuses any other parameter withINVALID_INPUTand names the allowed ones. The check runs after the access check, so a source the caller may not use still answers as a missing one.create_linkworks as before: it reads the params and the link carries none.linkandparams.check-configprints the list under the source's link.?.GET /sourcesandlist_sourcesname the list aslinkParams. Thecreate_linktool description changed, so MCP clients reconnect.packages/pivotkit-server/src/link-params.js.Docs
concepts/sharing.md#link-params: where parameters travel, a full configuration example, and how the query relates to the fragment'ssrc.paramsandallowParams. The host page applies "the query wins" and passes on only the listed names. A snippet shows how.security.md#link-params: query values land in access logs, history and theRefererheader. List only parameters whose values may show up there. The host page sendsReferrer-Policy: same-originorno-referrer.Docs checked: I searched
docs/and the package READMEs forcreate_link,views/link,linkKey,allowParamsandsrc.params.Tests
packages/pivotkit-server/test/link-params.test.js(10 tests): an allowed parameter lands in the query; encoding of& # + space ü; an existing query and hash route stay; another, unknown or claim-bound parameter and bad values are refused; a hidden source answers like a missing one; no list keeps today's behaviour; the configuration refusals;GET /sourcesand REST end to end; check-config.list_sourcesandcreate_linkwith params over Streamable HTTP.npm run lint,npm run types, the tests of pivotkit-server (779), pivotkit-mcp (100), pivotkit-report (109) and the repository tests (110),npm run pack:check,zensical build --strict. Linux, Windows, the browser suite and the container image run only in CI.Merge order
The upgrading section uses the heading "From 0.8.2 to the next release", the same one the rows route uses. It expects the 0.8.2 release first. This change and the rows route both touch
config.js,present.js,docs/openapi.json, the upgrading page,security.md,rest.md,sources.mdand the server changelog. The second of the two to merge needs a merge of main andnode scripts/openapi.js.Not in this change
create_linkgets params for a source without a list. Today the link carries none, silently.pivotkit-core/linkthat merges the query and the fragment.🤖 Generated with Claude Code