Skip to content

turbo-native-modules: specify that Native prefix is needed #4465

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

turbo-native-modules: specify that Native prefix is needed #4465

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3026f95
turbo-native-modules: specify that Native prefix is needed
maxgalbu Jan 27, 2025
b0b39eb
turbo-native-modules: newlines
maxgalbu Jan 27, 2025
c42819e
Update docs/turbo-native-modules.md
cortinico Jan 28, 2025
242c738
turbo-native-modules: update current version docs
maxgalbu Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/turbo-native-modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,10 @@ To create a specs file:
You can see all of the types you can use in your specification and the native types that are generated in the [Appendix](/appendix.md) documentation.
:::

:::info
If you want to change the name of your module and the related specs file, make sure to always use 'Native' as prefix (e.g. NativeStorage or NativeUsersDefault).
:::

Here is an implementation of the `localStorage` specification:

<Tabs groupId="language" queryString defaultValue={constants.defaultJavaScriptSpecLanguage} values={constants.javaScriptSpecLanguages}>
Expand Down