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

Add Pressable Component to the Documentation of Core-Components and API, User Interface Section #4022

Closed
totitoti7 opened this issue Feb 19, 2024 · 3 comments · May be fixed by #4049
Closed
Labels
Stale Issues/PR that are not getting much activity and are closer to be closed

Comments

@totitoti7
Copy link

Description

The current React Native documentation, specifically in the section that discusses User Interface components such as Button and Switch, does not include the Pressable component. Including Pressable would provide a more comprehensive overview of the interactive elements available in React Native, enhancing the documentation's utility and accessibility for developers.

What is the problem?

The omission of the Pressable component from this section may lead to a lack of awareness about this flexible alternative, which offers more customization and control over touch interactions compared to Button and Switch. This gap can hinder developers, especially newcomers, from exploring and utilizing Pressable in their projects.

How can we address it?

To rectify this, we should update the docs/components-and-apis.md file to include the Pressable component within the same section as Button and Switch. here is what the code can be updated to:

User Interface

These common user interface controls will render on any platform.

Why is it important?

Incorporating Pressable into the documentation is crucial because it:

  • Broadens the toolkit available to developers, promoting more flexible and creative UI designs.
  • Ensures developers are fully informed about the components at their disposal, leading to better decision-making in UI development.
  • Aligns with the goal of keeping the React Native documentation comprehensive and up to date with the framework's capabilities.

Who needs this?

This documentation update is beneficial for:

  • New learners who are building their foundational knowledge of React Native.
  • Experienced Android and iOS developers seeking to leverage React Native's full potential.
  • Developers looking to create more customized and interactive user interfaces.

When should this happen (use version numbers if needed)?

It would be ideal for this update to be included in the next documentation update cycle. If version numbers are applicable, aiming for inclusion in the upcoming release would ensure that the documentation remains current and comprehensive.

@cortinico
Copy link
Contributor

The current React Native documentation, specifically in the section that discusses User Interface components such as Button and Switch, does not include the Pressable component. Including Pressable would provide a more comprehensive overview of the interactive elements available in React Native, enhancing the documentation's utility and accessibility for developers.

Please go ahead and add Pressable in the page in a PR 👍

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 21, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

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

Successfully merging a pull request may close this issue.

2 participants