sea-orm
sea-orm copied to clipboard
Add more workspace setup information
Motivation
As a newcomer, I found it difficult to make VSCode understand the code written in the migration folder.
It is because the migration is not imported in the main crate.
Proposed Solutions
- Add functionality to
sea-orm-clito automatically add the following lines to the mainCargo.toml:
[dependencies]
sea-orm = {
# ...
}
migration = { path = "/path/to/migration/crate" }
- If 1 is not feasible, add some information about this in the documentation, preferably under the Installation & Configuration section.
Additional Information
The solution enables rust-analyzer to correctly identify the crate, while also providing auto-completion and code-checking.
I found the reference here, would be cool if it was highlighted a little more.
Hey @sungvzer, welcome!
As a newcomer, I found it difficult to make VSCode understand the code written in the
migrationfolder.
Do you mean VScode didn't provide any linting for symbols inside migration crate?
it is because the migration is not imported in the main crate.
I wonder which example are you referring to? Because all of the examples are with migration crate imported into the root carate - except for the basic example as it doesn't have migration crate in it.
I found the reference here, would be cool if it was highlighted a little more.
Do you have any thoughts on this? How should we highlight it and where? hahaa