Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @typespec/http from 0.47.0 to 0.59.0 #7865

Closed

Conversation

sylvainsf
Copy link
Contributor

snyk-top-banner

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
  • 0.59.0 - 2024-08-08

    @ typespec/compiler

    Bug Fixes

    • #3881 Fixes a bug where ending a non-terminal line in a multi-line comment with a backslash caused the next star to show up in the parsed doc string.
    • #4050 Allow using compact namespace form Foo.Bar when inside another namespace
      namespace MyOrg.MyProject {
        namespace MyModule.MySubmodule { // <-- this used to emit an error
          // ...
        }
      }
      
    • #3898 Fix decimal numeric with leading zeros
    • #4046 Fix type comparison of literal and scalar when in projection context
    • #4022 tsp compile --watch will not stop when a crash happens during compilation
    • #3933 Add const template parameter to get the precise lib type

    Bump dependencies

    • #3948 Update dependencies

    Features

    • #3906 Support completion for template parameter extending model or object value

      Example

      model User<T extends {name: string, age: int16}> {
      }
      alias user = User< {┆
                          | [age]
                          | [name]
      
    • #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 arrays

    Breaking 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 namespace MyOrg.MyProject.MyArea and model B in MyOrg.MyProject.MyArea2. With this change model A will now be in MyOrg.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

    • #3909 Fix HttpPart not respecting explicit part name by always using the property name
    • #3933 Fix some diagnostic not showing the right message

    Bump dependencies

    • #3948 Update 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-6570

      @ route("files{+path}") download(path: string): void;
      

    Deprecations

    • #3932 API deprecation: HttpOperation#pathSegments is deprecated. Use HttpOperation#uriTemplate instead.

    • #3932 Deprecated @ query({format: }) option. Use @ query(#{explode: true}) instead of form or multi format. Previously csv/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.

      - @ query({format: "form"}) select: string[];
      + @ query(#{explode: true}) select: string[];

    @ typespec/versioning

    Bug Fixes

    • #3911 Allow spreading a model that has props added in previous version
    • #3951 Fixes issue where spreading a versioned model as a parameter to an incompatible versioned operation would cause the compiler to crash.

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/rest

    Bump dependencies

    • #3948 Update dependencies

    Features

    • #3932 Add support for URI templates in routes

    @ typespec/openapi

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/openapi3

    Bug Fixes

    • #4046 Fix issue where operation example would produce an empty object when @ body/@ bodyRoot was used
    • #4046 Fix operation response body examples showing up for each response.
    • #3912 Fixes bug where union documentation was being applied to each union member in emitted output.
    • #3908 Fixes bug where circular references in unions caused an empty object to be emitted instead of a ref.

    Bump dependencies

    • #3948 Update dependencies

    Features

    • #3894 Add support for @ useRef on responses
    • #4020 Add support for encoding numeric types as string
    • #3890 @ extension used on the service namespace will set extension at the root of the document
    • #3932 Add support for URI templates in routes

    @ typespec/protobuf

    Bug Fixes

    • #3933 Fix some diagnostic not showing the right message

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/prettier-plugin-typespec

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/eslint-plugin

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/html-program-viewer

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/json-schema

    Bump dependencies

    • #3948 Update dependencies

    Breaking Changes

    • #3558 Updates @ 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 the Json<> 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:

    @ extension("x-example", #{ foo: "bar" })
    model Foo {}
    

    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, use typeof when passing in a scalar value.

    The following example demonstrates how to pass a scalar value that emits a JSON schema:

    @ extension("x-example", "foo")
    model Foo {}
    

    To preserve this same behavior, the above example can be updated to the following:

    @ extension("x-example", typeof "foo")
    model Foo {}
    

    @ typespec/internal-build-utils

    Bump dependencies

    • #3948 Update dependencies

    typespec-vs

    Bug Fixes

    • #4115 Fixed a router bug where paths would sometimes fail to match after a parameter was bound.

    typespec-vscode

    Bump dependencies

    • #3948 Update dependencies

    @ typespec/library-linter

    Bump dependencies

    • #3948 Update dependencies
  • 0.59.0-dev.11 - 2024-08-07
  • 0.59.0-dev.10 - 2024-08-07
  • 0.59.0-dev.9 - 2024-08-06
  • 0.59.0-dev.6 - 2024-08-05
  • 0.59.0-dev.5 - 2024-07-30
  • 0.59.0-dev.4 - 2024-07-24
  • 0.59.0-dev.3 - 2024-07-24
  • 0.59.0-dev.2 - 2024-07-22
  • 0.59.0-dev.1 - 2024-07-19
  • 0.59.0-dev.0 - 2024-07-17
  • 0.58.0 - 2024-07-17
  • 0.58.0-dev.6 - 2024-07-16
  • 0.58.0-dev.5 - 2024-07-08
  • 0.58.0-dev.4 - 2024-07-08
  • 0.58.0-dev.0 - 2024-06-13
  • 0.57.0 - 2024-06-13
  • 0.57.0-dev.8 - 2024-06-11
  • 0.57.0-dev.7 - 2024-06-03
  • 0.57.0-dev.6 - 2024-06-03
  • 0.57.0-dev.5 - 2024-06-03
  • 0.57.0-dev.4 - 2024-05-20
  • 0.57.0-dev.2 - 2024-05-09
  • 0.57.0-dev.1 - 2024-05-08
  • 0.57.0-dev.0 - 2024-05-08
  • 0.56.0 - 2024-05-08
  • 0.56.0-dev.11 - 2024-04-29
  • 0.56.0-dev.10 - 2024-04-23
  • 0.56.0-dev.9 - 2024-04-23
  • 0.56.0-dev.8 - 2024-04-23
  • 0.56.0-dev.7 - 2024-04-17
  • 0.56.0-dev.3 - 2024-04-15
  • 0.56.0-dev.2 - 2024-04-09
  • 0.56.0-dev.1 - 2024-04-04
  • 0.56.0-dev.0 - 2024-04-02
  • 0.55.0 - 2024-04-02
  • 0.55.0-dev.3 - 2024-03-19
  • 0.55.0-dev.2 - 2024-03-18
  • 0.55.0-dev.1 - 2024-03-06
  • 0.55.0-dev.0 - 2024-03-05
  • 0.54.0 - 2024-03-05
  • 0.54.0-dev.8 - 2024-03-04
  • 0.54.0-dev.7 - 2024-02-29
  • 0.54.0-dev.6 - 2024-02-28
  • 0.54.0-dev.5 - 2024-02-28
  • 0.54.0-dev.4 - 2024-02-28
  • 0.54.0-dev.3 - 2024-02-27
  • 0.54.0-dev.2 - 2024-02-15
  • 0.54.0-dev.0 - 2024-02-07
  • 0.53.0 - 2024-02-07
  • 0.53.0-dev.1 - 2024-01-26
  • 0.53.0-dev.0 - 2024-01-24
  • 0.52.1 - 2024-01-26
  • 0.52.0 - 2024-01-24
  • 0.52.0-dev.7 - 2024-01-22
  • 0.52.0-dev.6 - 2024-01-12
  • 0.52.0-dev.5 - 2024-01-11
  • 0.52.0-dev.4 - 2024-01-02
  • 0.52.0-dev.3 - 2023-12-23
  • 0.52.0-dev.2 - 2023-12-18
  • 0.52.0-dev.1 - 2023-12-13
  • 0.52.0-dev.0 - 2023-12-06
  • 0.51.0 - 2023-12-06
  • 0.51.0-dev.3 - 2023-11-21
  • 0.51.0-dev.2 - 2023-11-16
  • 0.51.0-dev.1 - 2023-11-15
  • 0.51.0-dev.0 - 2023-11-08
  • 0.50.0 - 2023-11-08
  • 0.50.0-dev.4 - 2023-11-06
  • 0.50.0-dev.3 - 2023-11-06
  • 0.50.0-dev.2 - 2023-10-26
  • 0.50.0-dev.1 - 2023-10-19
  • 0.50.0-dev.0 - 2023-10-12
  • 0.49.0 - 2023-10-12
  • 0.49.0-dev.7 - 2023-10-10
  • 0.49.0-dev.6 - 2023-10-07
  • 0.49.0-dev.5 - 2023-10-04
  • 0.49.0-dev.4 - 2023-09-27
  • 0.49.0-dev.3 - 2023-09-25
  • 0.49.0-dev.2 - 2023-09-21
  • 0.49.0-dev.1 - 2023-09-19
  • 0.49.0-dev.0 - 2023-09-13
  • 0.48.0 - 2023-09-13
  • 0.48.0-dev.6 - 2023-09-11
  • 0.48.0-dev.5 - 2023-08-30
  • 0.48.0-dev.4 - 2023-08-29
  • 0.48.0-dev.3 - 2023-08-28
  • 0.48.0-dev.2 - 2023-08-21
  • 0.48.0-dev.1 - 2023-08-17
  • 0.48.0-dev.0 - 2023-08-08
  • 0.47.0 - 2023-08-08
from @typespec/http GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade @typespec/http from 0.47.0 to 0.59.0.

See this package in npm:
@typespec/http

See this project in Snyk:
https://app.snyk.io/org/sylvainsf/project/1c6d6805-012f-4872-824f-6444fde9c055?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

Unit Tests

3 299 tests  ±0   3 293 ✅ ±0   3m 54s ⏱️ -6s
  263 suites ±0       6 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 47ac883. ± Comparison against base commit a58b8cb.

Copy link

codecov bot commented Aug 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.06%. Comparing base (a58b8cb) to head (47ac883).
Report is 84 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7865   +/-   ##
=======================================
  Coverage   61.05%   61.06%           
=======================================
  Files         523      523           
  Lines       27466    27466           
=======================================
+ Hits        16770    16772    +2     
+ Misses       9211     9210    -1     
+ Partials     1485     1484    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ytimocin ytimocin closed this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants