docs(react-native): TypeScript schema generation for .riv files - #821
Draft
mfazekas wants to merge 4 commits into
Draft
docs(react-native): TypeScript schema generation for .riv files#821mfazekas wants to merge 4 commits into
mfazekas wants to merge 4 commits into
Conversation
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.
WIP / draft — pending the runtime release that ships
rive-gen-types.New page documenting TypeScript schema generation in
@rive-app/react-native: generating.riv.d.tsfiles withnpx rive-gen-typesso artboard names, state machine names, view model names, property paths, and enum values are checked at compile time. Covers the quick start, what the generated schema contains, typing your own components withTypedRiveFile/TypedViewModelOf, workflow and CI guard, known limits, CLI reference, and troubleshooting.Added to the React Native nav after Data Binding. Some follow-ups (named enum types,
viewModelName-based generation, Rive CLI integration) are intentionally left out until they land.