-
Notifications
You must be signed in to change notification settings - Fork 332
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
Disabling any resolver on a Mongoose model fails to generate the schema #6989
Comments
If you want, we can open a PR with this fix after we have completed our testing with the rest of our models/projects |
So far this is working great! It even gave us the possibility of creating in advance types for our schemas that are embedded in more than one model. Previously, the first model that was using the schema create a type for it in the format With this fix in place, we can have models were all the resolvers are disabled to create types for our reusable schemas. |
We'd love to accept a PR :) |
When disabling resolvers in the .meshrc configuration files, the Mongoose handler would still try to generate the schema, then fail. Co-authored-by: Jean-Philippe Boily <jp.boily@axceta.com>
When disabling resolvers in the .meshrc configuration files, the Mongoose handler would still try to generate the schema, then fail. Co-authored-by: Jean-Philippe Boily <jp.boily@axceta.com>
When disabling resolvers in the .meshrc configuration files, the Mongoose handler would still try to generate the schema, then fail. Co-authored-by: Jean-Philippe Boily <jean-philippe.boily@axceta.com>
…ng schema (#6989) (#7034) * Fix: filter out disabled operations in Mongoose handler (#6989) When disabling resolvers in the .meshrc configuration files, the Mongoose handler would still try to generate the schema, then fail. Co-authored-by: Jean-Philippe Boily <jean-philippe.boily@axceta.com> * .. --------- Co-authored-by: Jean-Philippe Boily <jean-philippe.boily@axceta.com> Co-authored-by: Arda TANRIKULU <ardatanrikulu@gmail.com>
Hello!
We’ve stumbled upon this error while trying to disable resolvers on one of our Mongoose models:
To trigger this error, we used the following configuration in
.meshrc
:Our package versions:
We've managed to make a patch on the compiled code and are still testing it, but the problem seems to be gone, and we are able to move forward with our project.
Here is the diff that solved the problem:
(CC: @jpboily-axceta)
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: