chore: add react-native-keys in security section to secure keys in react native
Just added a react-native-keys package in the security section because this package can secure and manage ENVs than all other available solutions
Deploy Preview for react-native ready!
| Name | Link |
|---|---|
| Latest commit | 89d581b58d3ecf5479776b7c49ac72b0d5f2b217 |
| Latest deploy log | https://app.netlify.com/sites/react-native/deploys/645de8d19e938300085ae6a7 |
| Deploy Preview | https://deploy-preview-3720--react-native.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
@Simek ?
Hey @numandev1,
Security is a quite sensitive page, we usually do not add new statements or alter it content significantly, unless it's really needed.
In general, in React Native docs we try to avoid recommending one library, over others, it can be seen for example on the removed API/Component pages, where we link to the directory:
- https://reactnative.dev/docs/imagepickerios
Saying that, we might want to review and probably rewrite the paragraph with packages links on the Security page in near future, to match the pattern mentioned above.
So in case of your package, I would recommend adding it to the React Native directory instead, to gain more users and traction in the community, which also should yield more marketing value than mention on the security page:
- https://reactnative.directory