You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Live version: https://docs.nativescript.org/
4
4
5
5
---
6
6
7
-
This repository holds the source for the **latest** version of our docs. The theme and general functionality is being built in a different repo, this repo is purely focused on the content.
7
+
This repository holds the source for the **latest** version of our docs.
8
8
9
9
## Goals
10
10
@@ -29,9 +29,7 @@ This repository holds the source for the **latest** version of our docs. The the
29
29
Pick a topic/page that nobody is working on yet, create a new branch, add the necessary markdown file and an entry to `content/sidebar.ts`.
30
30
Open a draft PR and start working on the page. Once you are ready for feedback, mark the PR as ready for review. During the review process, address any feedback until the content is approved.
31
31
32
-
If you have any questions, feel free to ask them in your PR and ping [@rigor789](https://github.com/rigor789).
33
-
34
-
> **Note**: in the current stage of the beta docs, please try to only include a single page + the sidebar config change in a PR to make the review process easier, and reduce possible conflicts. Once we have the majority of the pages complete, we can focus on adding cross-links and references where necessary, and do any additional cleanup passes - at which point this requirement will be dropped.
32
+
If you have any questions, feel free to ask them in your PR.
Copy file name to clipboardExpand all lines: content/guide/choosing-an-editor.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ If you do choose to [try Visual Studio Code](https://code.visualstudio.com/), le
16
16
17
17
After you install Visual Studio Code, you can open projects using the editor's `File` → `Open` menu option, but there's an alternative option that works far better for command-line-based projects like NativeScript: the `code` command.
18
18
19
-
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows on Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
19
+
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows and Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
20
20
21
-
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of command to create a new NativeScript app and open it for editing.
21
+
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of commands to create a new NativeScript app and open it for editing.
Copy file name to clipboardExpand all lines: content/guide/code-sharing.md
+5-23Lines changed: 5 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,9 @@ If a "code sharing solution" is maintained by a framework that can often mean th
25
25
26
26
## Code Sharing Solutions
27
27
28
-
Here are a few solitions to **code-sharing**, each having their pros and cons.
28
+
Here are a few solutions to **code-sharing**, each having their pros and cons.
29
29
30
-
### Nrwl Nx DevTools with @nativescript/nx
30
+
### Nx with @nativescript/nx
31
31
32
32
[Learn More about @nativescript/nx](https://github.com/NativeScript/nx)
33
33
@@ -42,28 +42,10 @@ Here are a few solitions to **code-sharing**, each having their pros and cons.
42
42
43
43
- Learning curve if not used to Nx practices in general
44
44
45
-
### Nrwl Nx DevTools with @nstudio/xplat
45
+
### npm or yarn workspaces
46
46
47
-
[Learn more about @nstudio/xplat](https://nstudio.io/xplat)
48
-
49
-
**Pros:**
50
-
51
-
- It's centered around JavaScript/TypeScript (lesson 1 and 5 above)
52
-
- Uses standard build tooling like TypeScript or webpack to build code (lesson 2 above)
53
-
- No custom file extensions to deal with (lesson 3 above)
54
-
- Nx splits up "apps" and "libs" clearly identifying deployment/distribution targets "apps" that consume shared code "libs" (lesson 4 above)
55
-
- It builds upon @nativescript/nx to further scale it across more paradigms so it's a natural extension when needed if already working in Nx with @nativescript/nx
56
-
- Opinionated architecture is provided via xplat which helps to avoid common pitfalls from hard lessons learned in real world developments with cross platform mixtures
57
-
58
-
**Cons:**
59
-
60
-
- Learning curve if not used to Nx practices in general
61
-
- Learning curve if you have not developed applications in large codebases before
62
-
- Understanding the [basic fundamentals](https://nstudio.io/xplat/fundamentals/architecture) of the provided architecture
63
-
64
-
### Yarn workspaces
65
-
66
-
[Learn more about Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/)
47
+
-[Learn more about npm workspaces](https://docs.npmjs.com/cli/using-npm/workspaces/)
48
+
-[Learn more about Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/)
Replace the above placeholders with your actual Sentry details.
47
47
48
+
::: tip
49
+
If you are also doing XR development with Vision Pro or Meta Quest, you may want to additionally setup `SENTRY_PROJECT_SLUG_VISIONOS`, `SENTRY_DSN_VISIONOS`, `SENTRY_PROJECT_SLUG_QUEST`, and `SENTRY_DSN_QUEST`. The bundling config below demonstrates using a visionOS version string as an example. Meta Quest would use the standard Android versioning location of app.gradle.
50
+
:::
51
+
48
52
## Step 4: Configure Webpack
49
53
50
54
We will use Webpack to manage environment variables and source maps with plugins:
A plugin that allows you to authenticate users with biometrics, such as fingerprints, facial recognition, etc.
35
35
36
36
> **Note**
37
-
> This plugin replaces [@nativescript/fingerprint-auth](../fingerprint-auth).
37
+
> This plugin replaces [@nativescript/fingerprint-auth](../plugins/fingerprint-auth).
38
+
39
+
### Prerequisites:
40
+
41
+
Before you can verify a user’s biometrics, the device must already have biometric data (such as fingerprints or a face scan) enrolled at the system level. This enrollment is handled by the device’s operating system settings—your app or this plugin does not capture or store biometric data directly. Users must set up biometrics through their device’s security settings (e.g., `Settings` > `Security` > `Biometrics` on Android, or `Settings` > `Face ID` & `Passcode` on iOS).
42
+
43
+
### How it works:
44
+
45
+
When you call the plugin’s verification methods, the plugin asks the operating system to prompt the user for their enrolled biometric (fingerprint, face, etc.) and returns the result. The plugin never sees or manages the actual biometric data—only the OS does.
If you have an existing network security config, incorporate the configuration specified above into it.
228
+
229
+
#### iOS (Optional)
201
230
202
231
Dependending on your setup iOS may not be able to communicate with Detox off the bat. In that case, you need to add the following to your `Info.plist` file to allow for local networking requests.
0 commit comments