Skip to content

Close gaps in functionality between annotation-processor and Java TypeSpec generator - #50284

Draft
Alan Zimmer (alzimmermsft) wants to merge 1 commit into
Azure:mainfrom
alzimmermsft:CloseGapsBetweenAnnotationProcessorAndTypeSpec
Draft

Close gaps in functionality between annotation-processor and Java TypeSpec generator#50284
Alan Zimmer (alzimmermsft) wants to merge 1 commit into
Azure:mainfrom
alzimmermsft:CloseGapsBetweenAnnotationProcessorAndTypeSpec

Conversation

@alzimmermsft

Copy link
Copy Markdown
Member

Description

  • Added @FormParam URL-encoded bodies using FORM_ESCAPER.
  • Added header-collection expansion and correct dynamic-header precedence.
  • Added optional/non-string path handling and collection-query semantics.
  • Fixed unknown-length BinaryData, direct/sliced ByteBuffer, dynamic content types, JSON charset handling, and pre-serialized multipart bodies.
  • Added type-based RequestContext and SSE listener wiring.
  • Fixed response closure so eager responses close exactly once while streaming responses remain open.
  • Added text, standard Base64, primitive, enum, list, map, and nested generic response decoding.
  • Extended JsonSerializer.java, JsonWriter.java, and CoreUtils.java for typed collections, temporal values, decimals, enums, BinaryData, and ISO durations with day components.
  • Fixed SSE response-body ownership in OkHttpHttpClient.java.
  • Removed generated SuppressWarnings("cast"), enabled all previously disabled processor integration tests, aligned tests with processor beta.5/Core beta.12, and regenerated checked-in service implementations.
    Updated changelogs and added focused unit/integration coverage.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
34 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant