nextLink property should not be marked readOnly: true

[mikekistler]

A recent change in TypeSpec Azure adds readOnly: true to the nextLink property in a pageable list response.

readOnly: true is meaningless on a property of a response-only schema, and pageable list responses are always response-only -- they are never part of a request body.

We should not be including meaningless attributes in the OpenAPI that is generated from TypeSpec.

[jiaosummer]

Github PR - https://github.com/Azure/azure-rest-api-specs-pr/pull/17181

Currently ran npx tsv specification\standbypool\StandbyPool.Management will add readOnly": true to nextLink property. Otherwise, the typespec validation fails and show the errors as in- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3588838&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=0f4aa080-c997-58ca-481c-4930865ae0f8

Please help us to unblock. thanks

[markcowl]

@mario-guerra There is a current discussion about this with differing opinions, can you coordinate coming to consensus?

[mikekistler]

UPDATE

you can tweak between readOnly:true​ or no readOnly​ at spec level with
@@visibility(Azure.Core.Page.nextLink)​ for ARM
@@visibility(Azure.Core.CustomPage.nextLink)​ for Azure.Core.

---

Capturing a workaround shared in email:

There is a one-line change to a spec that will update the visibility of these types across the whole spec:

@@visibility(Azure.Core.Page.nextLink)​

as shown in this playground

[mario-guerra]

@mikekistler can this issue be closed?

[mikekistler]

Fixed by #549