Bump esbuild from 0.18.13 to 0.18.14 in /it/typescript#2945
Merged
github-actions[bot] merged 1 commit intoJul 18, 2023
Merged
Conversation
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.18.13 to 0.18.14. - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.18.13...v0.18.14) --- updated-dependencies: - dependency-name: esbuild dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
andrueastman
approved these changes
Jul 18, 2023
github-actions
Bot
deleted the
dependabot/npm_and_yarn/it/typescript/esbuild-0.18.14
branch
July 18, 2023 10:00
aqeelat
added a commit
to aqeelat/kiota
that referenced
this pull request
Jul 15, 2026
Phase 1 of microsoft#7815. Resolves JSON Schema 2020-12 $dynamicRef against $dynamicAnchor so recursive type hierarchies generate with the active extending type instead of degrading to UntypedNode. Resolution delegates to OpenApiWorkspace.ResolveDynamicAnchorInContext (shipped in OpenAPI.NET 3.9.0 via microsoft/OpenAPI.NET#2913 and microsoft#2945), addressing the review feedback on microsoft#7817 to move the resolution logic into the library's reference-resolution path rather than consumer-side helpers. KiotaBuilder keeps only a thread-local entry-point frame (the outermost schema being materialized) to supply as resolution context for the multi-candidate case, where the library's Target returns null because more than one schema declares the same $dynamicAnchor. - Bumps Microsoft.OpenApi / Microsoft.OpenApi.YamlReader to 3.9.0. - Extends IsSemanticallyMeaningful to treat $dynamicRef schemas as meaningful so array dispatch reaches the resolver. - Logs a warning when a $dynamicRef cannot be resolved instead of silently producing UntypedNode. Known limitation: when a base type declaring $dynamicAnchor is materialized standalone before any derived type (e.g. it is the response of another endpoint), dynamic-ref-typed properties resolve against the base instead of the derived type. The fallback is UntypedNode with a build-time warning. The fully correct fix is to emit a union over all candidate derived types -- tracked as Phase 3 in microsoft#7815. Verified across C#, TypeScript, Go, Python, and Java via the new parameterized integration test ResolvesRecursiveDynamicRefAsync; all existing unit tests pass.
aqeelat
added a commit
to aqeelat/kiota
that referenced
this pull request
Jul 16, 2026
Phase 1 of microsoft#7815. Resolves JSON Schema 2020-12 $dynamicRef against $dynamicAnchor so recursive type hierarchies generate with the active extending type instead of degrading to UntypedNode. Resolution delegates to OpenApiWorkspace.ResolveDynamicAnchorInContext (shipped in OpenAPI.NET 3.9.0 via microsoft/OpenAPI.NET#2913 and microsoft#2945), addressing the review feedback on microsoft#7817 to move the resolution logic into the library's reference-resolution path rather than consumer-side helpers. KiotaBuilder keeps only a thread-local entry-point frame (the outermost schema being materialized) to supply as resolution context for the multi-candidate case, where the library's Target returns null because more than one schema declares the same $dynamicAnchor. - Bumps Microsoft.OpenApi / Microsoft.OpenApi.YamlReader to 3.9.0. - Extends IsSemanticallyMeaningful to treat $dynamicRef schemas as meaningful so array dispatch reaches the resolver. - Logs a warning when a $dynamicRef cannot be resolved instead of silently producing UntypedNode. Known limitation: when a base type declaring $dynamicAnchor is materialized standalone before any derived type (e.g. it is the response of another endpoint), dynamic-ref-typed properties resolve against the base instead of the derived type. The fallback is UntypedNode with a build-time warning. The fully correct fix is to emit a union over all candidate derived types -- tracked as Phase 3 in microsoft#7815. Verified across C#, TypeScript, Go, Python, and Java via the new parameterized integration test ResolvesRecursiveDynamicRefAsync; all existing unit tests pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps esbuild from 0.18.13 to 0.18.14.
Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
af0fe32publish 0.18.14 to npmfd1ddfacss: implement bare:globaland:local5c23beecss: match other local/global implementations3dc8372css: disallow,in:localand:global7db1264css: add aglobal-cssloader with global symbols9ff3860css: source map tests can now be more accuratefeea007css: emit mappings for calc reductionse3f6eb8css: emit mappings for tokens9410725css: emit mappings for subclass selectorsc6e14efcss: emit mappings for nesting selectorsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)