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

entimport fails to generate uuid fields correctly #33

Open
tmc opened this issue May 27, 2022 · 1 comment
Open

entimport fails to generate uuid fields correctly #33

tmc opened this issue May 27, 2022 · 1 comment
Assignees

Comments

@tmc
Copy link
Contributor

tmc commented May 27, 2022

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()

@zeevmoney
Copy link
Contributor

Hi @tmc,

It is in the roadmap, not supported yet, this is a feature that is handled by schemast in ent contrib repo.

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

2 participants