Skip to content

Using the ClientMethodMapper extension points and hardening the paging parameter should-hide-check #7337

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

Merged
merged 9 commits into from
May 20, 2025

Conversation

anuchandy
Copy link
Member

@anuchandy anuchandy commented May 13, 2025

This PR has the following changes -

  1. Taking advantages of refactoring done in #7015 for ClientMethodMapper there by deleting the additional code we no longer needed.
  2. Centralizing the derivation and lookup of paging parameters to PagingMetadata and MethodPageDetails .
  3. Removing relaxed paging parameter lookup instead using common strict lookup in all places (azure, client-core etc..).

The AutoRest CI run is green with this PR's last commit [80bf3a9].

@microsoft-github-policy-service microsoft-github-policy-service bot added the emitter:client:java Issue for the Java client emitter: @typespec/http-client-java label May 13, 2025
@anuchandy anuchandy changed the title [WIP] Start using the extension point added for ClientMethodMapper [WIP] Start using the extension point added for ClientMethodMapper in #7015 May 13, 2025
@anuchandy anuchandy self-assigned this May 13, 2025
Copy link
Contributor

No changes needing a change description found.

@azure-sdk
Copy link
Collaborator

azure-sdk commented May 13, 2025

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@anuchandy anuchandy force-pushed the reuse-client-method-mapper branch 2 times, most recently from ca10d88 to c569a08 Compare May 17, 2025 07:31
@anuchandy anuchandy marked this pull request as ready for review May 17, 2025 08:15
@anuchandy anuchandy changed the title [WIP] Start using the extension point added for ClientMethodMapper in #7015 Using the ClientMethodMapper extension points and hardening the paging parameter should-hide-check May 17, 2025
@anuchandy anuchandy force-pushed the reuse-client-method-mapper branch from 442145b to 93c563a Compare May 18, 2025 17:26
Copy link
Contributor

@weidongxu-microsoft weidongxu-microsoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still reading...

@anuchandy anuchandy force-pushed the reuse-client-method-mapper branch from 93c563a to 61ace02 Compare May 20, 2025 00:24
@anuchandy anuchandy added this pull request to the merge queue May 20, 2025
Merged via the queue into microsoft:main with commit c45129e May 20, 2025
25 checks passed
@anuchandy anuchandy deleted the reuse-client-method-mapper branch May 20, 2025 15:44
ArcturusZhang pushed a commit to ArcturusZhang/typespec that referenced this pull request May 21, 2025
…g parameter should-hide-check (microsoft#7337)

This PR has the following changes -

1. Taking advantages of refactoring done in
[microsoft#7015](microsoft#7015) for
`ClientMethodMapper` there by deleting the additional code we no longer
needed.
2. Centralizing the derivation and lookup of paging parameters to
`PagingMetadata` and `MethodPageDetails
`.
3. Removing relaxed paging parameter lookup instead using common strict
lookup in all places (azure, client-core etc..).

The AutoRest CI run is
[green](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4878954&view=results)
with this PR's last commit [80bf3a9].
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emitter:client:java Issue for the Java client emitter: @typespec/http-client-java
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants