Docs: the field first, and the morph as something you turn on (to main) - #7
Merged
Merged
Conversation
…mentioned it There are two ways to format as you type, both before a frame is drawn: mode="mask" runs a compiled pattern in C++ on both platforms, and a transform worklet runs JS on the UI thread. The README covers both. The site covered only the worklet, and its props table did not know that mode takes 'mask' or that the four mask props and onChangeMask exist. A page for the masked field: the pattern notation, caller-defined slots, how literals are autocompleted and backspaced over, the four values onChangeMask hands back, and a short "native or worklet?" section that says which route to reach for. The worklets page now points at the native route for a fixed pattern, how-it-works mentions it beside the amount formatter, and getting-started lists it under where to go next. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The morph knob defaulted to on, but NitroInput is plain unless asked for `morph`, and the knob's default is also what the generated snippet leaves out. So the preview morphed while the snippet, which always names NitroInput, said nothing about it: copy it and the field did not morph. Off by default fixes both, and turning it on now writes `morph` into the snippet. `duration` hides with the morph like `easing` and `effect` do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Docs: the field first, and the morph as something you turn on
…lain-first-to-main
… both on main Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… removed #4 wrote "a plain NitroInput" as a link to /input/plain-field, and #6 folded that page into getting started and the morph page. The merge of the two built with a broken link. It points at the morph page now, which is where plain versus morph is explained. Co-Authored-By: Claude Fable 5.1 <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.
#6 was merged into
docs/worklet-eventstwenty minutes after #3 had already taken that branch tomain, so its content never reachedmain. This is the same work, merged ontomaincleanly (no conflicts with #4 or #5), plus the one row that was waiting on both:signPlacementon the props page.What #6 does, for reference:
/input/textand/input/plain-fieldredirect.TextInput. No Material references.numberOfLines/rows, growing,scrollEnabled,textAlignVertical,lineHeight.worklets.tsmodule comment lists all eight handlers.npm run buildindocs/passes on the merged result; every link and anchor resolves.🤖 Generated with Claude Code