Edit: Like when I import a mixin from another smithy file, in the same namespace, the vscode plugin is crying that its not in the same model. I fucking hate languages that want me to put everything in the same file.
You don't need to put it in the same file. I think you may be bumping into a bug in the Smithy LSP that prevents new files from being properly registered - try reloading the window / restarting vscode and see if it helps. If it doesn't, feel free to report what you're seeing in github.com/smithy-lang/smithy-language-server/ :)
@@kubukoz_ yeah it was mostly fake errors from the linting. The linter just doesn't work properly, especially with monorepos. Also the one for intelliJ doesn't work at all as it's not yet adapted to the smithy-build.json and expects gradle build.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
Edit: Like when I import a mixin from another smithy file, in the same namespace, the vscode plugin is crying that its not in the same model. I fucking hate languages that want me to put everything in the same file.
You don't need to put it in the same file. I think you may be bumping into a bug in the Smithy LSP that prevents new files from being properly registered - try reloading the window / restarting vscode and see if it helps. If it doesn't, feel free to report what you're seeing in github.com/smithy-lang/smithy-language-server/ :)
@@kubukoz_ yeah it was mostly fake errors from the linting. The linter just doesn't work properly, especially with monorepos. Also the one for intelliJ doesn't work at all as it's not yet adapted to the smithy-build.json and expects gradle build.