* feat: use shift for shortcuts. Swap onKeyStroke for useMagicKeys * refactor: simplify control shortcuts * Revert changes to input.ts * refactor: Make more DRY * Revert "refactor: Make more DRY" This reverts commit a508fcfb9d2fef0cd2635911bc57410989166a50. * Revert "Revert changes to input.ts" This reverts commit c47300d0104d09f9fa0ae9bc9e86e994f0a46206. * Revert "refactor: simplify control shortcuts" This reverts commit a867d6e34d06a7a6436ff4bdb6c4a7db94d3ca21. * Fix broken space * Refactor Viewer Controls and Keyboard Shortcuts * Fix keyboard shortcut mapping to handle string keys correctly * refactor: string enum * remove filters shortcut
ui-components
Speckle UI component library built with Vue 3 and relying on the Speckle Tailwind theme.
Setup
- Make sure you have
@speckle/tailwind-themeinstalled and set up with Tailwind - Install
@speckle/ui-components - In your tailwind config import
tailwindContentEntryfrom@speckle/ui-components/tailwind-configureand invoke it in thecontentsfield to ensure PurgeCSS is configured correctly. It requires the CJSrequireobject as its only parameter. If it isn't available (in an ESM environment), you can use node'screateRequire(). - Import
@speckle/ui-components/style.cssin your app. Ifexportsmap isn't supported you can also import from@speckle/ui-components/dist/style.css
Usage in Nuxt v3
It's suggested that you also install the @speckle/ui-components-nuxt Nuxt module. It will ensure that all of the Vue components can be auto-imported like components in nuxt's ./components directory. No need to import them manually anymore and you'll also get proper TS typing in your Vue templates out of the box!
Troubleshooting
Form validation doesn't work
It appears that in some scenarios Nuxt/Vite gets confused and bundles 'vee-validate' twice. To fix this add 'vee-validate' to vite.resolve.dedupe in your nuxt/vite config.
Build
Run yarn build
Development
Develop & test your components in Storybook - yarn storybook
Optionally you can also run yarn dev to run the Vite dev server which runs App.vue and in some special scenarios you might want to debug components there.
Troubleshooting
Styles don't work
Re-start storybook, it could be that you introduced a new tailwind class that was previously purged out