Skip to content
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.

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

Deprecated components should be clearly marked deprecated on the website #3996

Open
flanger001 opened this issue Jan 23, 2024 · 4 comments
Open
Labels
Stale Issues/PR that are not getting much activity and are closer to be closed

Comments

@flanger001
Copy link

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:

image

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:

image

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.

@lunaleaps
Copy link
Contributor

Great points! Is this something you'd be interested in helping out on?

@flanger001
Copy link
Author

Great points! Is this something you'd be interested in helping out on?

Most definitely!

@flanger001
Copy link
Author

@lunaleaps Should I open a PR? I don't know what all of the deprecated stuff is and would need some guidance on finding it.

Copy link

👋 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.

@github-actions github-actions bot added the Stale Issues/PR that are not getting much activity and are closer to be closed label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale Issues/PR that are not getting much activity and are closer to be closed
Projects
None yet
Development

No branches or pull requests

2 participants