678c75350c
* Update Section Box controls to include visibility
* Update reset v-if
* Update shortcut
* Added render requests so that section box updates are made visible
* Remove comments
* Exposed SectionToolEvent in the viewer
* Only show reset when change has been made to sectionbox
* gql
* Make state reactive
* Revert "Make state reactive"
This reverts commit
|
||
|---|---|---|
| .. | ||
| .vscode | ||
| assets | ||
| components | ||
| composables | ||
| layouts | ||
| lib | ||
| middleware | ||
| pages | ||
| plugins | ||
| public | ||
| server | ||
| tools | ||
| type-augmentations | ||
| utils | ||
| .env.example | ||
| .gitignore | ||
| .stylelintignore | ||
| Dockerfile | ||
| app.vue | ||
| codegen.ts | ||
| error.vue | ||
| eslint.config.mjs | ||
| log.info | ||
| nuxt.config.ts | ||
| package.json | ||
| postcss.config.js | ||
| readme.md | ||
| stylelint.config.js | ||
| tailwind.config.js | ||
| tsconfig.eslint.json | ||
| tsconfig.json | ||
readme.md
frontend-2 🏬
The replacement for our old Vue 2 Vue CLI frontend SPA app. This one's built with Vue 3, Nuxt 3, Tailwind and is server side rendered. Should be a faster and nicer experience both for our devs and our users!
Look at the nuxt 3 documentation to learn more.
Setup
Make sure to install the dependencies:
yarn install
And create an .env file from .env.example.
WSL2 on Windows
Remove the HOST env var from your .env file as its known to cause performance issues with the Nuxt dev server: https://github.com/nuxt/cli/issues/209
Development
Start the development server on http://localhost:8081
yarn dev
Typed GraphQL
Type your queries & fragments using the graphql() helper from ~~/lib/common/generated/gql and then run yarn gqlgen (or yarn gqlgen:watch to run it in watch mode) to generated TS typing information for these GQL documents.
More info: https://the-guild.dev/blog/unleash-the-power-of-fragments-with-graphql-codegen
Troubleshooting
ESLint results doesn't update after GQL type regeneration
Restart the ESLint plugin through VSCode's command palette, this is a bug with the ESLint plugin.
GraphQL codegen throws an error like "Unknown fragment XXX" or something else that doesn't make sense
Sometimes the codegen throws misleading errors and the issue is actually something completely different so I suggest removing the new graphql fragments/operations you've added one by one until the generation works again, to isolate the problematic graphql code. And then thoroughly investigate the fragments/operations you've added, because you might have a syntax error somewhere.
Production
Build the application for production:
yarn build
You can serve the production build locally by running yarn preview afterwards.
Checkout the deployment documentation for more information.