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

Use json as input for code generation #5

Closed
Tracked by #34
karatakis opened this issue Jun 16, 2022 · 2 comments
Closed
Tracked by #34

Use json as input for code generation #5

karatakis opened this issue Jun 16, 2022 · 2 comments

Comments

@karatakis
Copy link
Collaborator

Now we read plain token streams from sea orm generator.

We need to read json produced from sea schema to be more future proof.

Remove sea orm generator dependency and easier to test

@karatakis karatakis added this to the Prototype milestone Jun 16, 2022
@billy1624
Copy link
Member

As discussed on Discord. We'll skip the JSON layer and pass seaography_types::SchemaMeta directly into seaography_generator.

The dataflow would be: seaography_discoverer produce SchemaMeta then pass it to seaography_generator for the generation of async-graphql types.

@karatakis karatakis removed this from the Prototype milestone Jul 1, 2022
@karatakis karatakis mentioned this issue Aug 8, 2022
17 tasks
@karatakis
Copy link
Collaborator Author

OUT OF DATE, we depend on sea_orm entities

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