Adding config option for flag in sea-orm-cli generate entity

[aadi58002]

PR Info

• Closes Config file of sea-orm-cli generate entity command #1185

New Features

• Adds a option to have a config file for the generate entity sea-orm-cli command.

[aadi58002]

@tyt2y3 or @billy1624
can you review the PR and give feedback for changes?

[billy1624]

Hey @aadi58002, thanks for the initiative and for contributing!!

I agree that we should split the fields in GenerateSubcommands::Entity( ... ) into a separate struct (GenerateSubCommandsEntity) as you just did.

However, can we keep the field type in GenerateSubCommandsEntity untouched? I imagine the user will always provide the database_url and database_schema. The config file (if provided) will override all other options and flags. i.e. sea-orm-cli entity generate -url mysql://sea:sea@localhost/bakery -schema bakery -config my_config.json

[aadi58002]

Hey @aadi58002, thanks for the initiative and for contributing!!

I agree that we should split the fields in GenerateSubcommands::Entity( ... ) into a separate struct (GenerateSubCommandsEntity) as you just did.

However, can we keep the field type in GenerateSubCommandsEntity untouched? I imagine the user will always provide the database_url and database_schema. The config file (if provided) will override all other options and flags. i.e. sea-orm-cli entity generate -url mysql://sea:sea@localhost/bakery -schema bakery -config my_config.json

We can skip the url and schema field during de serialized i think which does make it so that database_url and database_scheme will not be de serialized from the config and will need to be provided from the cli.
e51d66d

[aadi58002]

@billy1624 can you review this PR?

[aadi58002]

@billy1624 or @tyt2y3 Can you review this PR and give feedback?