microsoft / microsoft/api-guidelines
Update how client's handle `nextlink`
Open
Nobody has claimed this yet.
Azure Guidelines
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
From convo w/Jeffrey Richter
I don't think we ever created a document on this (but we should update our guidelines). A client should apply its desired api-version to the nextLink either overwriting an api-version if it is there or appending the client's desired api-version if the nextLink does not have an api-version on it already. This is the same for LRO Operation-Location headers (we did address this in the new LRO guidelines).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.