You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is already available. but there is no way to configure the extension to look for the smithy-build.json file in any other location than the root directory. This leads to the inability to have a smithy folder in a project where you place the models and the smithy-build.json file. This structure is what all of the smithy tutorials and guides recommend so I thought I was doing something wrong when it wasn't working.
I could be wrong about this, please let me know.
If this is the case, I think some documentation should be added that makes this apparent.
The text was updated successfully, but these errors were encountered:
You should be able to specify a root path using the vscode extension config option smithyLsp.rootPath. But yea it isn't well documented right now.
Really we need to have the extension look for smithy-build.json files from the working directory, though. That way you wouldn't have to specify the path yourself.
@milesziemer I've tried setting smithyLsp.rootPath in my workspace settings to the directory containing our smithy-build.json relative to the root of my workspace, but I'm not getting any LSP functionality.
When I change it to an absolute path it does work, but that is not a viable solution for me because I have multiple branches of my repository checked out in different paths. Is it possible to configure it as a relative path?
Not sure if this is already available. but there is no way to configure the extension to look for the smithy-build.json file in any other location than the root directory. This leads to the inability to have a smithy folder in a project where you place the models and the smithy-build.json file. This structure is what all of the smithy tutorials and guides recommend so I thought I was doing something wrong when it wasn't working.
I could be wrong about this, please let me know.
If this is the case, I think some documentation should be added that makes this apparent.
The text was updated successfully, but these errors were encountered: