Repository navigation
docs(build): split the Swift and Raycast tutorials in two - #760
Merged
Merged
Conversation
aicayzer
marked this pull request as ready for review
November 1, 2026 00:18
aicayzer
force-pushed
the
docs/tutorials-to-limit
branch
from
November 1, 2026 00:19
293704b to
8b03be3
Compare
aicayzer
force-pushed
the
docs/tutorials-to-limit
branch
from
November 1, 2026 00:44
8b03be3 to
562a454
Compare
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.
Summary
The Swift and Raycast tutorials each become two, so each part is one sitting under the 1,500-word tutorial limit, and their ceilings are removed. The Swift app now takes its queue's answers in one step, and its second part shows the core's filter model and link reading instead of code an app would write itself.
Closes #716
Closes #717
Closes #729
Closes #710
#717's link bounds are in #754, and #710's Define a type and Change a type parts are in #759. Merge those with or before this one.
Changes
queue.takeAnswered(), which clears every answered write in one step, with a Take Answers button and an Answered section. The Show your notes step says why the rows usetitleand points toitems.displays(of:)for naming items of any type. Renaming and the verdict step move to part two.linkParts(in:)anditems.linkCandidates(of:in:), saving the text so the copy makes itsreferencesedge; and find notes by title withFilterExpression,encoded()andinit(decoding:), keeping the search between launches.createItem, a note form, and a run.listTypesandgetType, field controls titled by each field'slabel(no longer made from the field's name), a form built from the chosen type, thetype_not_permittedrefusal, and a key widened to tasks.build/meta.jsonlists each second part after its first;page-limits.jsongives both new pages the tutorial kind and removes the two ceilings. Build's landing card and the Overview say the Raycast tutorial saves notes.Testing
pnpm test: 828 passed, on main after docs(connectors): describe v0.0.8 status words and core fields #757 and docs(glossary): hold the Glossary page to GLOSSARY.md #758.pnpm buildandpnpm exec vite preview: all four pages looked at at 375 px (no sideways scroll) and at 1,280 px, with the sidebar listing each part after the first; their.mdcopies carry every step.Links.swift,FilterModel.swift,LiveQuery.swift,WorkingCopy.swift) and marfa v0.0.50:device/link-candidates-bound,-unresolvedanddevice/body-link-by-title(a new link by title staysunresolveduntil the instance's lookup answers on save, then the copy makes the edge);device/body-link(referencesedges);FieldDefinition.labelinopenapi.json(a type read answers a label for every field).Notes for reviewers
device/link-candidates-unresolved.field.label, which closes the Raycast half of Describe field labels, a type's plural and the phone format #715 that docs(build): move device files to a guide, bring build guides to limit #759 left.src/lib/page-limits.json, some next to each other, so the later ones may need a rebase as the earlier merge.Checklist