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
and then run sbt smithy4sUpdateLSPConfig, my dependency is not automatically added to the smithy-build.json.
And so in vscode with the disneystreaming smithy plugin, the editor is not aware of the shapes from my library. In .smithy.lsp.log, there are errors like Use statement refers to undefined shape about the shapes from my library.
If I manually add the dependency to the smithy-build.json file like my.test:core-types_2.13:0.1.0-SNAPSHOT, it works.
The text was updated successfully, but these errors were encountered:
If memory serves me correctly, this task uses dependencies defined in the Smithy4s configuration. Something like the following, if you don't use that, then the task won't see the dependencies.
I think we should capture these dependencies too. The sbt plugin makes their smithy specs available at build-time, so it's fair game to want them in smithy-build.json
I have a project that defines some smithy shapes which I have published as a library locally. The project looks like:
modules/core/src/main/smithy/core.smithy
build.sbt
I am publishing with
sbt publishM2
.When I add this dependency to another project like:
along with:
and then run
sbt smithy4sUpdateLSPConfig
, my dependency is not automatically added to thesmithy-build.json
.And so in vscode with the disneystreaming smithy plugin, the editor is not aware of the shapes from my library. In
.smithy.lsp.log
, there are errors likeUse statement refers to undefined shape
about the shapes from my library.If I manually add the dependency to the
smithy-build.json
file likemy.test:core-types_2.13:0.1.0-SNAPSHOT
, it works.The text was updated successfully, but these errors were encountered: