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
Deprecated components should be clearly marked deprecated on the website and they are not.
What is the problem?
When developing a React Native app with navigation using the guides on the website (https://reactnative.dev/docs/navigation), the browser console emits a warning "Button is deprecated. Please use Pressable." among others:
None of these components are actually marked as deprecated on the website. #3421 addresses Button, but it is the softest possible recommendation I've ever seen and can hardly be considered a deprecation notice.
How can we address it?
Clearly mark deprecated components and props, using stronger language, and provide clear resolution paths. As a visual suggestion:
On a related note, accessibility labels are not only for blindness and this language could be made more inclusive. Not trying to be a wokescold, just making a note.
Why is it important?
If I am learning the most up-to-date version of a framework with the most up-to-date version of that framework's documentation and the prescribed solutions causes my browser to emit a deprecation notice, I am not confident I can trust that documentation and therefore am not confident I can trust my knowledge.
Who needs this?
Everyone, but particularly learners.
When should this happen (use version numbers if needed)?
As soon as a component or prop is marked deprecated.
The text was updated successfully, but these errors were encountered:
👋 Hey there, it looks like there has been no activity on this issue in the last 90 days. Has the issue been fixed, or does it still require the community attention? This issue will be closed in the next 7 days if no further activity occurs. Thank you for your contributions.
Description
Deprecated components should be clearly marked deprecated on the website and they are not.
What is the problem?
When developing a React Native app with navigation using the guides on the website (https://reactnative.dev/docs/navigation), the browser console emits a warning "Button is deprecated. Please use Pressable." among others:
None of these components are actually marked as deprecated on the website. #3421 addresses Button, but it is the softest possible recommendation I've ever seen and can hardly be considered a deprecation notice.
How can we address it?
Clearly mark deprecated components and props, using stronger language, and provide clear resolution paths. As a visual suggestion:
On a related note, accessibility labels are not only for blindness and this language could be made more inclusive. Not trying to be a wokescold, just making a note.
Why is it important?
If I am learning the most up-to-date version of a framework with the most up-to-date version of that framework's documentation and the prescribed solutions causes my browser to emit a deprecation notice, I am not confident I can trust that documentation and therefore am not confident I can trust my knowledge.
Who needs this?
Everyone, but particularly learners.
When should this happen (use version numbers if needed)?
As soon as a component or prop is marked deprecated.
The text was updated successfully, but these errors were encountered: