Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ByteBardOrg/AsyncAPI.NET
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: vnext
Choose a base ref
...
head repository: ByteBardOrg/AsyncAPI.NET
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fix/reference-fallbacks
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 21 files changed
  • 1 contributor

Commits on Oct 24, 2026

  1. fix!: resolve local references outside the components, in both versions

    Local references that do not point at a registered component, such as into
    another channel, operation or message, are resolved from the document. That
    fallback crashed or failed for most of them:
    
    - 2.x documents were resolved against their 3.x re-serialization, so 2.x
      pointers into publish/subscribe and channel parameters never resolved,
      and 2.x payloads lost their schemaFormat. They now resolve against the
      original document, and the payload's schemaFormat is kept in scoped temp
      storage for the 2.x version service to apply.
    - Correlation ID and operation trait fragments had no loader, and server
      variable, tag, external docs, reply and reply address references had no
      fallback, so reading threw or reported an error.
    - The walker skipped server variable and operation references.
    - A 2.x channel referencing another root channel crashed while registering
      components. It now points at the same channel, and is written with that
      channel's address in 2.x.
    
    Writing kept references whose target the written version does not have,
    such as a 2.x "#/channels/a/publish/message" written as 3.x, or a 3.x
    "#/operations/op/traits/0" written as 2.x. Those are now written inline; a
    reference that resolves in the written document stays a reference. The
    writer also sees what the reader resolved outside the components, and 2.x
    writes referenced tags and external docs inline instead of dropping them.
    
    BREAKING CHANGE: JsonPointerExtensions is removed; use JsonPointer.Find.
    VisualBean committed Oct 24, 2026
    Configuration menu
    Copy the full SHA
    fe66369 View commit details
    Browse the repository at this point in the history
  2. fix: inline a 2.x channel reference whose target is not written

    A 2.x channel reference is written with its target's address, since 2.x
    keys channels by address. When the target is not one of the document's
    channels, for example because it was removed after reading, that address
    points nowhere and did not match the reference, so it was left dangling.
    Such a reference now keeps its own pointer, which is found dangling and
    written inline.
    VisualBean committed Oct 24, 2026
    Configuration menu
    Copy the full SHA
    9e499f4 View commit details
    Browse the repository at this point in the history
Loading