search

Tahul / nuxt-edgedb

💽 Nuxt 3 integration for EdgeDB
71 stars 7 forks source link

Path of initial generation of defaults inconsistent with generate edgeql-js path #26

Open NicBelanger23 opened 7 months ago

NicBelanger23 commented 7 months ago

When running "@edgedb/generate edgeql-js" the generated files are placed into /dbschema/edgeql-js/.

However, nuxt is looking for files in /dbschema/query-builder/.

Workaround is to move files into /dbschema/query-builder/ by hand after generating

Recreation: after following the setup process, run npm run dev. Running the project for the first time, the automatically generated folder for defaults is /dbschema/query-builder/. preforming @edgedb/generate edgeql-js after migrating changes places new defaults into /dbschema/edgeql-js/.

Workarounds: move files into /dbschema/query-builder/ by hand after generating or add --out dbschema/query-builder to match what the package is doing.

Both of the workarounds are not obvious and lead me into thinking I was doing something wrong. I believe the nuxt package of edge db should use the /dbschema/edgeql-js/ path for consistency's sake.

Tahul commented 5 months ago

Hello;

I just released O.47 that drops generation from the module logic.

You can now run a CLI that guides you through everything you need to generate using:

npx nuxt-edgedb-module

Could you let me know if that helped you?