v0.0.30

What's Changed

• Update main (2024.03) by @kubukoz in #52

Full Changelog: v0.0.29...v0.0.30

v0.0.29: Input/Ouput fix

What's Changed

• chore: fix direct smithy-build version by @kubukoz in #47
• Avoid substring if not suffixed by @daddykotex in #49
• misc updates to fix gpg signing by @daddykotex in #50

Full Changelog: v0.0.28...v0.0.29

v0.0.28

What's Changed

• Update smithy to 1.37.0 (smithy-lang#119) by @kubukoz in #46

Full Changelog: v0.0.27...v0.0.28

v0.0.27

What's Changed

Features a bunch of upstream changes such as:

• Dependency resolution using Coursier has been replaced with Aether (Maven's dependency resolver), and it uses the smithy-cli implementation of dependency resolution under the hood
• Updates smithy-* libraries from 1.31.0 to 1.35.0
• Updates the smithy-translate formatter with some bugfixes (now tracking v0.3.10)

Note: if you're using an LSP client other than the disneystreaming/vscode-smithy one, you may need to update it to provide an explicit main class. For inspiration, see how vscode-smithy did it.

When upgrading, you might need to change the content of your smithy-build.json file. The changes you'll need to do need to include at least:

1. defining a top level version field. eg: "version": "1.0" - related change
2. you can't use ivy latest.stable (or other ivy style version range), so you'll need to pin the version of the dependencies that you depend on
3. Aether's resolution has different semantics, e.g. in version choice: for example, it uses the "shortest path" algorithm to determine which version of a transitive library should be used, i.e. picks the one that's "closest" to the dependency you're pulling in.

Full Changelog: v0.0.26...v0.0.27

v0.0.26

What's Changed

• More verbosity in logs/output panel in case of errors smithy-lang#105

• Fix matching inline inputs/outputs with operations smithy-lang#111

Full Changelog: v0.0.25...v0.0.26

v0.0.25

What's Changed

• Show version on startup by @kubukoz in #42

Full Changelog: v0.0.24...v0.0.25

v0.0.24

What's Changed

• Update smithytranslate-formatter to 0.3.4 (awslabs#103)
• Implement basic textDocument/documentSymbol (awslabs#99)
• Upgrade to Smithy 1.31.0 (awslabs#104)

Full Changelog: v0.0.23...v0.0.24

v0.0.23

What's Changed

• Fix off-by-one error when loading projects in smithy-lang#101
• Fix location for elided members in smithy-lang#98

Full Changelog: v0.0.22...v0.0.23

v0.0.22: Formatting

This release brings in formatting to the language server. This means that editor can leverage the language server to format Smithy file.

In VS Code, you can use the formatting action, shown below:
.

If you're using format on save, but want to disable it for Smithy, you can use the following setting:

{
  "[smithy]": {
    "editor.formatOnSave": false
  }
}

---

The release is tagged 0.0.22. By default the latest.stable version is pulled by the extension but you can override this behaviour. For instance, if you'd like to keep using the previous version, you can tweak the behaviour of the extension using the following in smithy-build.json at the root of your project:

{
  "languageServer": "com.disneystreaming.smithy:smithy-language-server:x.x.x"
}

You can also use other language server jar like software.amazon.smithy:smithy-language-server:0.2.3 for example.

v0.0.21: Sync from upstream

This release should fix an issue where language server does not run custom validators when loading the model.

What's Changed

• Bump actions version by @daddykotex in #35
  Full Changelog: v0.0.20...v0.0.21