nativescript-community / ui-drawer

NativeScript plugin that allows you to easily add a side drawer (side menu) to your projects.
https://nativescript-community.github.io/ui-drawer/
Apache License 2.0
24 stars 12 forks source link

Transition to new plugin seed #11

Closed keerl closed 3 years ago

keerl commented 3 years ago
  1. Clone repo: git clone https://github.com/nativescript-community/ui-drawer.git

  2. Checkout branch: git checkout feature/plugin-seed

  3. Initialize submodules: git submodule update --init

  4. Install dependencies: npm i (or pnpm i or whatever you do)

  5. Try out interactive menu with npm start. You don't have to use this, but I thought it was pretty neat (and easy) way to be able to quickly see and search through the common scripts.

Screen Shot 2021-05-19 at 5 14 53 AM

  1. Build plugin by selecting build.all from the interactive list or run npm run build.all.
  2. Run demo. Use interactive menu to select demo or go into any demo sub-directory and run ns run android --no-hmr or ns run ios --no-hmr. Demos should look like the below video.

https://user-images.githubusercontent.com/24727492/118804428-e946c580-b861-11eb-85b5-80f5a54e2783.mov

  1. Automatically redirect to a specific demo on start-up. Use the --env.redirect=[demo_path] where [demo_path] is the path property in the install script for the specific demo snippet. See here

    • To run from top-level use: npm run demo.vue.android -- --env.redirect=development
    • To run from demo directory: ns run android --no-hmr --env.redirect=development
  2. Open the plugin in VS Code and confirm there are no typing errors or any other sort of error in the editor in the demo-snippets directory. If errors do appear, run the demo they are associated with and then restart VS Code and hopefully they are gone.

  3. When changing demos, only the demo-snippets directory should be modified. The actual demo directory should stay the same as they are (or will be) common across multiple plugins. If something needs to be changed in a demo, we can update that, but we will also apply the same change to all the other plugins using it.