[Snyk] Upgrade @typespec/http from 0.47.0 to 0.59.0 #7865
Closed
+8
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @typespec/http from 0.47.0 to 0.59.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 90 versions ahead of your current version.
The recommended version was released on 21 days ago.
Release notes
Package name: @typespec/http
@ typespec/compiler
Bug Fixes
Foo.Bar
when inside another namespacetsp compile --watch
will not stop when a crash happens during compilationconst
template parameter to get the precise lib typeBump dependencies
Features
#3906 Support completion for template parameter extending model or object value
Example
#4020 Add support for encoding numeric types as string
#4023 Warn when using
\
in config file field that expect a path.#3932 Add
ArrayEncoding
enum to define simple serialization of arraysBreaking Changes
#4050 Fix issue where naming a namespace with the same name as the blockless namespace would merge with it instead of creating a subnamespace like any other name would.
namespace MyOrg.MyProject;
namespace MyOrg.MyProject.MyArea {
model A {}
}
namespace MyArea2 {
model B {}
}
Previously model
A
would end-up in namespaceMyOrg.MyProject.MyArea
and modelB
inMyOrg.MyProject.MyArea2
. With this change modelA
will now be inMyOrg.MyProject.MyOrg.MyProject.MyArea
. To achieve the previous behavior the above code should be written as:namespace MyOrg.MyProject;
namespace MyArea {
model A {}
}
namespace MyArea2 {
model B {}
}
@ typespec/http
Bug Fixes
HttpPart
not respecting explicit part name by always using the property nameBump dependencies
Features
#4046 API: Expose
properties: HttpProperty[]
on operation parameter and response which reference all the properties of interest(Body, statusCode, contentType, implicitBodyProperty, etc.)#3932
@ route
can now take a uri template as defined by RFC-6570Deprecations
#3932 API deprecation:
HttpOperation#pathSegments
is deprecated. UseHttpOperation#uriTemplate
instead.#3932 Deprecated
@ query({format: })
option. Use@ query(#{explode: true})
instead ofform
ormulti
format. Previouslycsv
/simple
is the default now.Decorator is also expecting an object value now instead of a model. A deprecation warning with a codefix will help migrating.
@ typespec/versioning
Bug Fixes
Bump dependencies
@ typespec/rest
Bump dependencies
Features
@ typespec/openapi
Bump dependencies
@ typespec/openapi3
Bug Fixes
@ body
/@ bodyRoot
was usedBump dependencies
Features
@ useRef
on responses@ extension
used on the service namespace will set extension at the root of the document@ typespec/protobuf
Bug Fixes
Bump dependencies
@ typespec/prettier-plugin-typespec
Bump dependencies
@ typespec/eslint-plugin
Bump dependencies
@ typespec/html-program-viewer
Bump dependencies
@ typespec/json-schema
Bump dependencies
Breaking Changes
@ extension
decorator to support TypeSpec values in addition to types.In previous versions of the json-schema emitter, the
@ extension
decorator only accepted types as the value. These are emitted as JSON schemas. In order to add extensions as raw values, types had to be wrapped in theJson<>
template when being passed to the@ extension
decorator.This change allows setting TypeSpec values (introduced in TypeSpec 0.57.0) directly instead.
The following example demonstrates using values directly:
This change results in scalars being treated as values instead of types. This will result in the
@ extension
decorator emitting raw values for scalar types instead of JSON schema. To preserve the previous behavior, usetypeof
when passing in a scalar value.The following example demonstrates how to pass a scalar value that emits a JSON schema:
To preserve this same behavior, the above example can be updated to the following:
@ typespec/internal-build-utils
Bump dependencies
typespec-vs
Bug Fixes
typespec-vscode
Bump dependencies
@ typespec/library-linter
Bump dependencies
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: