Skip to content

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

@NicBelanger23

Description

@NicBelanger23

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions