What's the suggested way for a existing SeaORM user to adopt seaography?

[billy1624]

Currently, I see the seaography assume there exists a schema reside in one of the supported database engine. Then, SeaORM entities and async-graphql types will be generated by seaography.

But what if a existing SeaORM user wish to introduce async-graphql support into their existing codebase? What's the suggested way of doing it? Should we provide a way to generate async-graphql types only? Instead of only provide a CLI that generate both at the same time?

[karatakis]

That's a great question.

A proposed way is to allow cli to accept a parameter that points to sea orm entities folder, and when it is used we skip generating sea orm and do the following:

1. parse the sea orm entities folder
2. populate seaography schema
3. generate graphql entities

What's your thougs on that approach ?

[tyt2y3]

I think that's what we have talked about before comes to place. We have to break down the code generator into different stages, where stage 1 is schema discovery and stage 2 is code generation.

Actually, what does the stage 2 takes as input? If that's a SeaQuery schema representation, then it should be possible for sea-orm-cli to produce that and invoke the seaography library.

That say, most of the integration should be done inside sea-orm-cli

[billy1624]

Actually, what does the stage 2 takes as input? If that's a SeaQuery schema representation, then it should be possible for sea-orm-cli to produce that and invoke the seaography library.

Stage 2 takes SeaQuery table create statement.

Are you suggesting we simply skip generating SeaORM entities and generate graphql entities only?

For example, assumed we have a entity crate in a cargo workspace which contains all the SeaORM entities. Then, we generate two more crates to provide async-graphql supports:

• graphql crate: contains all graphql entities, depends on async-graphql and entity crate
• graphql-api crate: home of web API code, depends on async-graphql-<WEB_API> and entity crate

[tyt2y3]

Sounds like a workable plan

[billy1624]

Thoughts? @karatakis

[karatakis]

@billy1624 with #114 we have completely isolated seaography from sea-orm entity generation. If you provide the seaography CLI with the folder of SeaORM entities it generates the GraphQL API without the need of modifications.