Doug Parker 6e299da8cf feat(forms): hard-code readOnlyHint and untrustedContentHint for WebMCP implicit signal forms ...

Signal forms can safely assume `{readOnlyHint: false, untrustedContentHint: false}` given their context. A form _must_ alter page DOM (or else how would a user interact with it) and is therefore definitionally side-effectful. We also assume returned content is trusted, given it is currently hard-coded or derived from application errors.

In the future, we might want to consider cases where application errors are explicitly untrusted or where application developers choose to customize the response text with something which might be untrusted. For now, that's out of scope and we'll worry about it when a compelling use case arises.

2026-09-01 09:39:20 -07:00

..

signals

feat(forms): hard-code readOnlyHint and untrustedContentHint for WebMCP implicit signal forms

2026-09-01 09:39:20 -07:00

src

refactor(forms): type async validator subscription

2026-08-24 10:00:19 -07:00

test

fix(core): replace all hasOwnProperty usages with Object.hasOwn

2026-08-18 09:17:18 -07:00

BUILD.bazel

build: cleanup workspace deps

2026-04-23 11:38:26 -07:00

index.ts

refactor: update license text to point to angular.dev (#57901)

2024-09-24 15:33:00 +02:00

package.json

build: update dependency @mcp-b/webmcp-types to v4

2026-07-07 09:46:23 -07:00

PACKAGE.md

docs(forms): update package docs for Signal Forms graduation

2026-06-22 16:29:18 -04:00

public_api.ts

refactor: update license text to point to angular.dev (#57901)

2024-09-24 15:33:00 +02:00