Compile Error - Unable to find the put() method in the ClaimsPolicyRequestBuilder class in Microsoft Graph SDK version 6.28.0 (beta)

[avenger20005]

Describe the bug

Our application uses the put() method to update custom claims in the ClaimsPolicyRequestBuilder class. However, after rebuilding the application, it started failing and showing compile errors. The build process is now pulling in version 6.28.0 of the Microsoft Graph SDK, and the put() method is no longer available in that version. For some reason, the put() method seems to be missing from the updated SDK

Expected behavior

The put() method should be available in the ClaimsPolicyRequestBuilder class to maintain backward compatibility.

How to reproduce

Use version 6.28.0 of the Microsoft Graph SDK (beta) to reproduce the error.

SDK Version

6.28.0

Latest version known to work for scenario above?

6.26.0

Known Workarounds

We started using the older 6.26.0 version, and the put() method is available in that version.

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

[baywet]

Hi @avenger20005

Thank you for using the SDK and for reaching out.

This regression was introduced with c0176d9

@andrueastman do you think this could be related to the hidi/yoko alignment work?

6.27.0 which has the put operation was generated on 2024-12-31 with hidi 1.4.17
6.28.0 which does not have the put operation was generated on 2025-01-07 with hidi 1.4.18

The only differences between those two versions are this microsoft/OpenAPI.NET@6129ac8

It does seem like we have one and two transformations being applied here.

What I'd like to confirm is whether I might have missed/messed up the backports of fixes on the 1.X branch.

[andrueastman]

After taking a look at this, looks like this change was missing from the v1 branch of the conversion library. microsoft/OpenAPI.NET.OData#647

As much as the transformations exist, the library support for placing both put and patch methods for a path was not in the V1 library.

Created microsoft/OpenAPI.NET.OData#647 to address this in V1 of the library. And we should have the fix showing up in the library updates latest next week.

[andrueastman]

Looks like this is now resolved with the generation changes present in #1119. And should be available on the next release of the library.