Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
NicBelanger23 opened this issue Apr 23, 2024 · 0 comments

Comments

@NicBelanger23
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant