We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I believe entimport does not currently match the field.UUID API which accepts a second argument.
entimport
I just got a field generated as: field.UUID("fooer_id").Optional(uuid.UUID{})
field.UUID("fooer_id").Optional(uuid.UUID{})
where I believe the appropriate syntax is field.UUID("fooer_id", uuid.UUID{}).Optional()
field.UUID("fooer_id", uuid.UUID{}).Optional()
The text was updated successfully, but these errors were encountered:
Hi @tmc,
It is in the roadmap, not supported yet, this is a feature that is handled by schemast in ent contrib repo.
schemast
Sorry, something went wrong.
zeevmoney
No branches or pull requests
I believe
entimport
does not currently match the field.UUID API which accepts a second argument.I just got a field generated as:
field.UUID("fooer_id").Optional(uuid.UUID{})
where I believe the appropriate syntax is
field.UUID("fooer_id", uuid.UUID{}).Optional()
The text was updated successfully, but these errors were encountered: