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
{{ message }}
Repository navigation
Commit 5bcea1d
Browse filesBrowse the repository at this point in the historyBrowse files
Merge branch 'main' into feat/refactor-icon-button-component
Port main's IconButton changes into the Material 3 Expressive rewrite:
- 48dp hit slop via getMinInteractiveSizeHitSlop, with a hitSlop override
(none when disabled or without a touch handler)
- role prop, and an image role on web for a labelled, handler-less button
- touchable fills the container so content stays centered
- touchable clips its own ripple, so the hit slop is not clipped
- a disabled icon takes the disabled color over iconColor
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,15 +101,27 @@ To preview the documentation, run `yarn docs dev` in the project root.
101
101
102
102
### Publishing a release
103
103
104
-
We use [release-it](https://github.com/webpro/release-it) to automate our release. If you have publish access to the NPM package, run the following from the main branch to publish a new release:
104
+
We use [release-it](https://github.com/webpro/release-it) to automate our release. If you have publish access to the NPM package, run the following from the main branch, always with the exact version you want to publish:
105
105
106
106
```sh
107
-
yarn release
107
+
yarn release 6.0.0-beta.0 --dry-run
108
+
yarn release 6.0.0-beta.0
109
+
```
110
+
111
+
- Always pass the version. A bare `yarn release` applies the bump the commit history recommends, which can be a stable or major version you did not intend. npm never accepts the same version twice, so a wrong version cannot be taken back.
112
+
- Start with the dry run. Before running it for real, check the compare range in the changelog heading it prints (for example `v6.0.0-alpha.0...v6.0.0-alpha.1`) and the `--tag` on the `npm publish` line.
113
+
- The npm tag and the GitHub prerelease flag follow the version: `6.0.0-beta.0` is published under the `beta` tag as a GitHub prerelease, `6.0.0` under `latest` as a regular release.
114
+
- The GitHub release is created as a draft. Once `npm publish` has succeeded, add the release notes and publish the draft:
NOTE: You must have a `GITHUB_TOKEN` environment variable available. You can create a GitHub access token with the "repo" access [here](https://github.com/settings/tokens).
111
121
112
-
Releases from main also deploy the example app via EAS. If there were no native code changes, it'll ship an OTA update.
122
+
You also need to be logged in to npm with an account that can publish the package: check with `npm whoami`, and run `npm login` if it fails.
123
+
124
+
Publishing the GitHub release also deploys the example app via EAS, so keep the release a draft until npm has the package. If there were no native code changes, it'll ship an OTA update.
| 6.x (`main`, published under the `alpha` tag until 6.0.0) | Yes |
8
+
| The latest 5.x release | Yes |
9
+
| Older 5.x releases and earlier majors | No |
10
+
11
+
## Reporting a vulnerability
12
+
13
+
Please don't report security problems in public issues, pull requests or discussions.
14
+
15
+
Report them privately through GitHub instead: on the repository's Security tab, click "Report a vulnerability", or go straight to https://github.com/callstack/react-native-paper/security/advisories/new. Include what is affected (the version and the component or API), how to reproduce it, and what an attacker could do with it.
16
+
17
+
The maintainers will reply in the advisory, work on a fix there with you, and credit you when it is published, unless you'd rather not be named.
Copy file name to clipboardExpand all lines: docs/5.x/docs/guides/fonts.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,7 +152,7 @@ If you're using TypeScript use `as const` when defining `fontConfig`.
152
152
In the latest version fonts in theme are structured based on the `variant` keys e.g. `displayLarge` or `bodyMedium` which are then used in`Text`'s component throughout the whole library.
153
153
154
154
:::info
155
-
The default `fontFamily` is different per particular platfrom:
155
+
The default `fontFamily` is different per particular platform:
Copy file name to clipboardExpand all lines: docs/5.x/docs/guides/migration-guide-to-5.0.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Below you can find the most important information about the components whose API
14
14
15
15
### Installation
16
16
17
-
- The `v5` has been oficially released as a stable version, which means it will be installed by default from the `npm`. In order to do that, open a Terminal in your project's folder and run:
17
+
- The `v5` has been officially released as a stable version, which means it will be installed by default from the `npm`. In order to do that, open a Terminal in your project's folder and run:
18
18
19
19
```bash npm2yarn
20
20
npm install react-native-paper
@@ -26,7 +26,7 @@ npm install react-native-paper
26
26
npm install react-native-safe-area-context
27
27
```
28
28
29
-
Additionaly for `iOS` platform there is a requirement to link the native parts of the library:
29
+
Additionally for `iOS` platform there is a requirement to link the native parts of the library:
30
30
31
31
```bash
32
32
npx pod-install
@@ -165,7 +165,7 @@ Take a look at the suggested replacement diff:
165
165
166
166
### Configure fonts
167
167
168
-
The existing utility called `configureFonts` was adjusted to help users configure their theme fonts in both version, that's why that function, as of today, is going to accept the object with the follwing properties as an argument:
168
+
The existing utility called `configureFonts` was adjusted to help users configure their theme fonts in both version, that's why that function, as of today, is going to accept the object with the following properties as an argument:
169
169
170
170
```ts
171
171
configureFonts(params);
@@ -476,7 +476,7 @@ With the latest version, there is a possibility to specify whether `Drawer.Secti
476
476
477
477
#### FAB
478
478
479
-
Additionaly`FAB` may be applied in one of three available sizes, thanks to new prop `size`:
479
+
Additionally`FAB` may be applied in one of three available sizes, thanks to new prop `size`:
480
480
481
481
-`small` - FAB with small height (40),
482
482
-`medium` - Appbar with default medium height (56),
0 commit comments