dooboo-ui-legacy

DEPRECATED

This project ends with dooboo-ui@0.0.80 and dooboo-ui-legacy@1.0.0 which are the same packages. This project is continued in dooboo-ui from version 0.1.0. There is additional notice on why we made this decision. The main purpose to speed up the project.

We love react-hooks and willing to share our react-native ui components built in functional components using hooks. Also the dooboo-ui-legacy is built on top of our favorite stacks like emotion, typescript, jest, react-testing-library, expo, storybook, and so on.

Documentation

• Hosted in github pages

Contributing to dooboo-ui

• See also
  • dooboolab's vision-and-mission
  • dooboolab's code of conduct
• Contributing
  • Please run yarn pre so that the packages are prepared.
    • If you are having trouble, try to run yarn install-packages.
  • Try to make awesome UI components and test them in storybook. Ensure to test in platforms we provide which are iOS, android and web. Then it's all good to go for pull request. Give it a try 🌼.
• While implementing UI components you should run yarn watch in order to build typescript files dynamically while implementing. This is currently the best solution to sync with your typescript code using package.json. If you find something more efficient, please give a pull request.

Usage

We aim to support react-native ui components in all platforms and we are currently targeting iOS, android and web. If you read issue on plan for unifying dooboo-ui, you can see in more detail how we want to drive this project.

Thememing

Follow the README_THEME

Compatibility

package	version
react	>=16.13
react-native	>=0.62
emotion	*

List of independent components in @dooboo-ui/*

Below elements are not included in dooboo-ui package since it depends on other packages that may overload its package.

• CalendarCarousel
• Charts
• GiftedChat
• Snackbar
• theme
• TinderCard

Troubleshoot

Workaround when you face error in expo web

You need to set webpack for using "dooboo-ui" in expo-web.

1. Install @expo/webpack-config in your expo's project. yarn add @expo/webpack-config or npm install @expo/webpack-config

2. Create webpack.config.js in root path and Add below code. See issue below for more details.

   ```javascript
   const createExpoWebpackConfigAsync = require('@expo/webpack-config');
   
   module.exports = async function(env, argv) {
     const config = await createExpoWebpackConfigAsync(
       {
         ...env,
         babel: {
           dangerouslyAddModulePathsToTranspile: [
             'dooboo-ui',
           ],
         },
       },
       argv
     );
     return config;
   };
   ```
   

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Backers

Please be our Backers.

Contributing

Please make sure to read the Contributing Guide before making a pull request. Thank you to all the people who helped to maintain and upgrade this project!

License