-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support for field.Strings/Ints #248
Comments
I believe i'm impacted by a similar issue when trying to use
I'm additionally confused why I'm unable to use |
Agree with @matoszz, the only annotation that I've found will get field.JSON to work with entoas is something like:
as described here: ent/ent#3573 (comment) Whilst that will generate an openapi.json file, it then causes issues in ogent with:
Is there a way to have JSON.field describe a json object that entoas and ogent are happy with? |
running ent codegen: execute template "ogent/responses": template: response.tmpl:17:6: executing "ogent/responses" at <setFieldExpr $f $n "ret" "e">: error calling setFieldExpr: unexpected type: "" Is this the reason to use field.JSON? |
A schema I'm working with has a few ent fields of type Strings or Ints (an array in OAS). Right now, codegen baila with a confusing error that I've narrowed down to no support for these types.
Is that something you've just not got around to (in which case, shall I submit a PR once I have coded it) or is it a conscious decision for another reason?
Thanks in advance!
The text was updated successfully, but these errors were encountered: