Closed theoephraim closed 3 months ago
Name | Link |
---|---|
Latest commit | 0bfa59554d594f4dea6134f6ebf32eefe664263f |
Latest deploy log | https://app.netlify.com/sites/signup-api/deploys/666a562691eb8f000822157b |
Name | Link |
---|---|
Latest commit | 0bfa59554d594f4dea6134f6ebf32eefe664263f |
Latest deploy log | https://app.netlify.com/sites/dmno/deploys/666a562692164d0008446e0a |
Deploy Preview | https://deploy-preview-92--dmno.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
By default, the
DMNO_CONFIG
andDMNO_PUBLIC_CONFIG
globals are not accessible within the template section of a vue component. You can work around this by assigning the config value to a variable, but it feels a bit annoying...We can make it work but requires a little work to tell TypeScript about it and to wire the globals into the vue compiler.
Examples are present for both for vanilla vue app and vue in astro.
Unfortunately, I dont think there is going to be a way to have a plugin do this, so will need to be done by the user, but it is simple enough.