[Snyk] Upgrade @typespec/compiler from 0.56.0 to 0.57.0 #1
Conversation
Snyk has created this PR to upgrade @typespec/compiler from 0.56.0 to 0.57.0. See this package in npm: @typespec/compiler See this project in Snyk: https://app.snyk.io/org/abdulrahman305/project/2d7e0832-afc9-498b-aaf9-735e1eddc8b5?utm_source=github&utm_medium=referral&page=upgrade-pr
|
👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: As a reminder, here are some helpful tips on how we can collaborate together:
|
|
Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect. Current plan usage: 103.59% Have feedback or need help? |
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @typespec/compiler from 0.56.0 to 0.57.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 23 versions ahead of your current version.
The recommended version was released on 21 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-BRACES-6838727
SNYK-JS-MICROMATCH-6838728
Release notes
Package name: @typespec/compiler
-
0.57.0 - 2024-06-13
- #3399 Preserve leading whitespace in fenced blocks in doc comments
- #3566 [API] Do not run decorators on cloned type if the original type wasn't finished
- #3522 Fix EINVAL error when running
- #3371 Numeric not handling trailing zeros and causing freeze(e.g.
- #3451 Emitter framework: fix losing context when referencing circular types
- #3517 Fix application of
- #3488 Add
- #3401 Update dependencies - May 2024
-
-
-
-
-
-
-
-
-
-
- #3022 Using a tuple type as a value is deprecated. Tuple types in contexts where values are expected must be updated to be array values instead. A codefix is provided to automatically convert tuple types into array values.
- #3022 Using a model type as a value is deprecated. Model types in contexts where values are expected must be updated to be object values instead. A codefix is provided to automatically convert model types into object values.
- #3022 Decorator API: Legacy marshalling logic
- #3022 Update Flow Template to make use of the new array values
- #3401 Update dependencies - May 2024
-
-
- #3292 Add
- #3022 Update to support new value types
- #3409 Using
- #3255 If a property were marked with @ added on a later version, the logic that said it was originally added on the first version was erroneously removed, resulting in incorrect projections.
- #3401 Update dependencies - May 2024
- #3022 Update types to support new values in TypeSpec
- #3401 Update dependencies - May 2024
- #3401 Update dependencies - May 2024
- #3342 Add support for new multipart constructs in http library
- #3574 Emit diagnostic when an invalid type is used as a property instead of crashing.
- #3401 Update dependencies - May 2024
- #3022 Add support for new object and array values as default values (e.g.
- #3022 Update to support new value types
- #3561 Corrected cross-package reference behavior in some buggy cases.
- #3401 Update dependencies - May 2024
- #3401 Update dependencies - May 2024
- #3401 Update dependencies - May 2024
- #3401 Update dependencies - May 2024
- #3022 Add support for values
- #3398 Fix decorators application for union variants
- #3022 Update to support new value types
- #3430 The emitted JSON Schema now doesn't make root schemas for TypeSpec types which do not have the @ jsonschema decorator or are contained in a namespace with that decorator. Instead, such schemas are put into the $defs of any root schema which references them, and are referenced using JSON Pointers.
- #3401 Update dependencies - May 2024
- #3557 Add support for @ OneOf decorator.
- #3401 Update dependencies - May 2024
- #3461 Support Arm64
- #3401 Update dependencies - May 2024
- #3533 Enhance logging and trace
- Support "Developer: Set Log Level..." command to filter logs in TypeSpec output channel
- Add "typespecLanguageServer.trace.server" config for whether and how to send the traces from TypeSpec language server to client. (It still depends on client to decide whether to show these traces based on the configured Log Level.)
- More logs and traces are added for diagnostic and troubleshooting
- #3385 Add 'TypeSpec: Show Output Channel' command in VSCode extension
- #3401 Update dependencies - May 2024
-
0.57.0-dev.28 - 2024-06-13
-
0.57.0-dev.27 - 2024-06-12
-
0.57.0-dev.26 - 2024-06-11
-
0.57.0-dev.25 - 2024-06-11
-
0.57.0-dev.24 - 2024-06-11
-
0.57.0-dev.23 - 2024-06-11
-
0.57.0-dev.22 - 2024-06-11
-
0.57.0-dev.21 - 2024-06-11
-
0.57.0-dev.20 - 2024-06-11
-
0.57.0-dev.19 - 2024-06-10
-
0.57.0-dev.18 - 2024-06-05
-
0.57.0-dev.17 - 2024-06-04
-
0.57.0-dev.16 - 2024-06-03
-
0.57.0-dev.15 - 2024-05-29
-
0.57.0-dev.13 - 2024-05-20
-
0.57.0-dev.10 - 2024-05-17
-
0.57.0-dev.8 - 2024-05-16
-
0.57.0-dev.7 - 2024-05-16
-
0.57.0-dev.6 - 2024-05-10
-
0.57.0-dev.5 - 2024-05-09
-
0.57.0-dev.4 - 2024-05-08
-
0.57.0-dev.0 - 2024-05-08
-
0.56.0 - 2024-05-08
- #3170
- #3212 Fix: augmenting template model property could result in sending invalid argument to decorator
- #3188 Fix: Do not crash when trying to access member of aliased expressions
- #3185 Fix tsp init hanging when done due to unclosed connection
- #3151 IDE: Fix completion of statement keywords
- #3287 Templated interface extending another templated interface shouldn't run decorator on their operations
- #3290 Model with an optional property should not satisfy a constraint with that property required. (
- #3163 Fix: Model with spread indexer shouldn't validate explicit properties
- #3227 Stop running decorators on partially instantiated operations(When interface is instantiated but not the operation)
- #3180 Fix issue where directives were not parsed to the leaf node in multi-segment Namespace segments.
- #3243 Fix calling
- #3216 Fix compiler crash when using an invalid
- #3246 Internals: Use node built-in
- #3169 Update dependencies
- #3035
- #3183 Show template parameters when hovering on an operation template
- #3191 [API] Add new
- #3196 Fix password flow defining
- #3190 Fix
- #3218 Fix:
- #3169 Update dependencies
-
-
-
-
- #3264 Fix crash when
- #3169 Update dependencies
- #3169 Update dependencies
- #2945 Add support for new
- #3169 Update dependencies
- #3218 Fix:
- #3169 Update dependencies
- #2945 Add support for new
- #3169 Update dependencies
- #3169 Update dependencies
- #3169 Update dependencies
- #3169 Update dependencies
- #3191 Add
- #3169 Update dependencies
- #3169 Update dependencies
- #3169 Update dependencies
- #3169 Update dependencies
from @typespec/compiler GitHub release notes@ typespec/compiler
Bug Fixes
tsp code installconst a = 100.0)@ paramdoc tag on operation create withop isto override upstream docPickPropertiestype to dynamically select a subset of a modelBump dependencies
Features
#3280 Support completion for Model with extended properties
Example
model Device {name: string;
description: string;
}
model Phone extends Device {
┆
} | [name]
| [description]
#3280 Support completion for object values and model expression properties.
Example
model User {name: string;
age: int32;
address: string;
}
const user: User = #{name: "Bob", ┆}
| [age]
| [address]
#3375 Allow
@to be escaped in doc comment with\#3022 Add syntax for declaring values. See docs.
Object and array values
@ dummy(#{ name: "John", age: 48, address: #{ city: "London" } aliases: #["Bob", "Frank"] })Scalar constructors
scalar utcDateTime {init fromISO(value: string);
}
model DateRange {
minDate: utcDateTime = utcDateTime.fromISO("2024-02-15T18:36:03Z");
}
#3527 Add support for
@ propdoc comment tag to describe model properties#3422 Formatter: Indent or dedent multiline strings to the current indentation
#3460 Hide deprecated items from completion list
#3443 Support completion for keyword 'extends' and 'is'
Example
model Dog ┆ {}| [extends]
| [is]
scalar Addresss ┆
| [extends]
op jump ┆
| [is]
interface ResourceA ┆ {}
| [extends]
model Cat<T ┆> {}
| [extends]
#3462 Linter
allrulesets is automatically created if not explicitly provided#3533 More logs and traces are added for diagnostic and troubleshooting in TypeSpec language server
Deprecations
model Test {// Deprecated
values: string[] = ["a", "b", "c"];
// Correct
values: string[] = #["a", "b", "c"];
model Test {// Deprecated
user: {name: string} = {name: "System"};
// Correct
user: {name: string} = #{name: "System"};
With the introduction of values, the decorator marshalling behavior has changed in some cases. This behavior is opt-in by setting the
valueMarshallingpackage flag to"new", but will be the default behavior in future versions. It is strongly recommended to adopt this new behavior as soon as possible.Example:
Will now emit a deprecated warning because
valueis of typevalueof stringwhich would marshall toNumericunder the new logic but asnumberpreviously.To opt-in you can add the following to your library js/ts files.
@ typespec/http
Bug Fixes
Bump dependencies
Features
#3342 Add new multipart handling. Using
@ multipartBodywithHttpPart<Type, Options>. See multipart docs for more information.#3462 Use new compiler automatic
allruleset instead of explicitly provided one@ typespec/versioning
Bug Fixes
@ madeRequireddecorator@ removedon member types and@ addedon containing type could result in errorsBump dependencies
@ typespec/rest
Bug Fixes
Bump dependencies
@ typespec/openapi
Bump dependencies
@ typespec/openapi3
Bug Fixes
Bump dependencies
Features
decimals: decimal[] = #[123, 456.7];)@ typespec/protobuf
Bug Fixes
Bump dependencies
@ typespec/prettier-plugin-typespec
Bump dependencies
@ typespec/eslint-plugin
Bump dependencies
@ typespec/html-program-viewer
Bump dependencies
Features
@ typespec/json-schema
Bug Fixes
Bump dependencies
Features
@ typespec/internal-build-utils
Bump dependencies
typespec-vs
Features
typespec-vscode
Bump dependencies
Features
@ typespec/library-linter
Bump dependencies
@ typespec/compiler
Bug Fixes
--nostdlibflag will now work by only applying to optional standard library types{foo?: string}cannot be assigned to a constraint of{foo: string})tsp installon windows due to recent NodeJS breaking change to fix vulnerability.istarget in an interface operation templatefetchAPI that is now stable since node18.13.0Bump dependencies
Features
getEncodereturns the fully qualified enum member name if using a custom enum.sourceModelsproperty to model@ typespec/http
Bug Fixes
authorizationUrlinstead oftokenUrl@ pathparam mapping when spreading a record in operation parameters@ pathproperty shouldn't be applicableMetadata if the visibility containsReadBump dependencies
Breaking Changes
#2945 Empty model after removing metadata and applying visibility always results in "void"
This means the following case have changed from returning
{}to no bodyWorkaround: Use explicit
@ body#2945 Implicit status code always 200 except if response is explicitly
voidSolution: Add explicit
@ statusCode#2945
@ bodymeans this is the bodyThis change makes using
@ bodymean this is the exact body and everything underneath will be included, including metadata properties. If metadata properties are present on the body, a warning will be logged.Use
@ bodyRootif you want to only change where to resolve the body from.#2945 Properties are not automatically omitted if everything was removed from metadata or visibility
Solution: use
@ bodyIgnore@ typespec/versioning
Bug Fixes
@ serviceappears inside a versioned namespaceBump dependencies
@ typespec/rest
Bump dependencies
Features
@ bodyRootand@ bodydistinction@ typespec/openapi
Bump dependencies
@ typespec/openapi3
Bug Fixes
@ pathproperty should be included in unreachable modelsBump dependencies
Features
@ bodyRootand@ bodydistinction@ typespec/protobuf
Bump dependencies
@ typespec/prettier-plugin-typespec
Bump dependencies
@ typespec/eslint-plugin
Bump dependencies
@ typespec/html-program-viewer
Bump dependencies
Features
sourceModelsproperty to model view@ typespec/json-schema
Bump dependencies
@ typespec/internal-build-utils
Bump dependencies
typespec-vs
No changes, version bump only.
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: