Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Tracking ant-design-mobile-rn 5.0
See original GitHub issue🌄 Overview:
This issue is to track development on ant-design-mobile-rn 5.0 : the revitilization update 🏆 and has come out of a previous discussion here.
The goal of this project is to revitalize ant-design-mobile-rn with the vision of being a 1:1 component library to ant-design.
ant-design offers world class enterprise components for React.js. The react-native community needs ant-design components to bring enterprise-level components to mobile platforms, as not many libraries offer enterprise-level components for react-native.
Support and development on ant-design-mobile-rn has died out slowly since this library has been maintained by individual developers, but none-the-less we stand on the shoulders of giants and strictly follow the ant-design design language.
This project will detail all of the ant-design components and APIs that we have left to make ant-design-mobile-rn up-to-date with ant-design.
This will be a long journey, but it must be done.
🎯 Goals:
-
Update
ant-design-mobile-rnto include all (or most) of the components inant-design. -
Add some new mobile-only components to the library – if possible
-
Completely revamp the docs to more accurately reflect categorization and documentation of new and old components.
📑 The details:
I have performed an initial grouping, comparing the existing ant-design-mobile-rn components that match up with ant-design.
Most of the unassigned components (i.e., components that don’t have a 1:1 matchup to ant-design are mobile-only, or components that only make sense on mobile devices (for example… the native pickers).
| Unassigned components from ant-design-mobile-rn |
|---|
| ActionSheet |
| SwipeAction |
| SearchBar |
| NoticeBar |
| PickerView |
| Picker |
| Toast |
| SegmentedControl |
| Flex |
| WingBlank |
| WhiteSpace |
Below is the main progress table.
The complete column shows if the Component or group of components is complete.
The ant-design components and ant-design-mobile-rn components (assigned) columns link to the respective components in each library.
The Issue Link column is a link to the issue that tracks on a deeper level discussion and development of the component. An issue can be created for each component or component group as we get to it.
I will work on a PR overhauling the docs, to properly categorize components as ant-design and coordinate with progress on the component-level to test and update component APIs in the docs.
I know @1uokun has started on component dev for the following components see here, maybe we can start with form ? Let me know.
To keep this thread clear, only comment about updates to the master list. For discussion on development of a new component or a re-factor of an existing component, create the issue for that discussion and dev…next, comment here so I can update the master list with the link to the issue or feature.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:17 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
expo support🎉
Checkout the official @ant-design/react-native App on Expo which uses all of the
ant-design-mobile-rncomponents.考虑到 antd-mobile v5 现在 beta 了，感觉再等等，让他跑一段时间再考虑移植 mobile-rn 比较适合。
我看现在 Table 里是想 rn 直接对标 antd。感觉这样不是很适合，UX 什么的应该对标 antd-mobile 才对。