docs: notify link placeholders - {recordUrl}, {inboxUrl}, {appUrl} - #22
Open
delchev wants to merge 1 commit into
Open
docs: notify link placeholders - {recordUrl}, {inboxUrl}, {appUrl}#22delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
A notification that cannot be acted on gets ignored, and the notify block had no documented way to carry the way back into the application - so an author's only option was pasting a route into the body, encoding a layout the intent does not own. Mirror the specification's new subsection: the three-placeholder table, the reserved-name rule, "an intent never spells a route", why the path belongs to whatever renders the application, and the fan-out scoping. Adds the reference index row.
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.
Mirrors IntentFile/intent-specification#22 onto the site.
A notification that cannot be acted on is a notification that gets ignored, and the notify block had no documented way to carry the way back into the application — so an author's only option was pasting a route into the body, encoding a layout the intent does not own.
docs/spec/glue.md— a new Links back to the application section under the notify block: the three-placeholder table, the reserved-name rule, "an intent never spells a route", an::: infocontainer on why the path belongs to whatever renders the application, and the fan-out scoping ({recordUrl}links the row).docs/reference.md— the index row.Anchors verified against the built HTML (
#links-back-to-the-application-recordurl-inboxurl-appurl);npm run docs:buildclean.Please review alongside the specification PR — happy to adjust wording before either lands.