Releases: kubukoz/smithy-playground
v0.3.6
New features:
textDocument/documentSymbol
has been implemented, which is used for several features in VS Code like breadcrumbs, document outline, as well as searching symbols within a workspace.
Example:
The feature works when the file parses, with no requirement to typecheck correctly.
What's Changed
- Update weaver-cats, weaver-discipline, ... to 0.7.15 by @scala-steward in #70
- Define range index by @kubukoz in #71
- Add document symbol provider by @kubukoz in #72
Full Changelog: v0.3.5...v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.1
v0.2.0
Language server
The extension is now implemented by means of a language server. For users, this shouldn't have significant impact, but it enables several improvements in the codebase, as well as a plugin mechanism. In case of issues, let me know!
What's Changed
Full Changelog: v0.1.5...v0.2.0
v0.1.3
v0.1.2
Deprecation warnings
When a deprecated field or union member is used (or if the target shape used by them is deprecated), it'll be highlighted as a warning with the deprecation tag (text strikethrough).
This also applies to enum values that were parsed by value instead of name (see #45 from v0.1.1.
Deprecated operations/services aren't handled in a special way yet. (this was added in 0.3.8)
What's Changed
-
Update smithy4s-aws-http4s, ... to 0.14.1 by @scala-steward in #47
-
Update cats-effect to 3.3.14 by @scala-steward in #50
-
Update sbt-converter to 1.0.0-beta39 by @scala-steward in #49
-
Update sbt-tpolecat to 0.4.0 by @scala-steward in #52
Full Changelog: v0.1.1...v0.1.2
v0.1.1
v0.0.27
What's Changed
More verbose completion descriptions
Previously, you'd see the types of the fields you're getting completions for:
Now you'll get more context, e.g. for a string MyString
you'll know that it's a String:
UUID support
UUIDs are now supported in queries (written in string literals). There are also completions which insert a random UUID (similar to timestamp completions).
Timestamp errors
Previously, you would never see a timestamp parsing failure, due to a bug in smithy4s. There is now a workaround for that, so you'll immediately know if you mistype a timestamp.
The underlying issue in smithy4s has been fixed and will be released in the 0.14.0 release.
Full Changelog: v0.0.26...v0.0.27