Define behaviour of RestClient#request when user specifies an X-Ably-Version header
#144
Comments
|
➤ Automation for Jira commented: The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3564 |
lawrence-forooghian
added a commit
that referenced
this issue
May 1, 2023
There’s still a question of how this method is meant to behave if the user also specifies an `X-Ably-Header` header in the `headers` parameter. But it’s a question that equally applied before adding the `version` parameter, so I’ve captured it in a separate issue #144. Same comment as 69e1973 re needing to update "replaced in" spec version before merging integration branch into `main` applies here too.
lawrence-forooghian
added a commit
that referenced
this issue
May 1, 2023
There’s still a question of how this method is meant to behave if the user also specifies an `X-Ably-Header` header in the `headers` parameter. But it’s a question that equally applied before adding the `version` parameter, so I’ve captured it in a separate issue #144. Same comment as 69e1973 re needing to update "replaced in" spec version before merging integration branch into `main` applies here too.
lawrence-forooghian
added a commit
that referenced
this issue
May 2, 2023
There’s still a question of how this method is meant to behave if the user also specifies an `X-Ably-Header` header in the `headers` parameter. But it’s a question that equally applied before adding the `version` parameter, so I’ve captured it in a separate issue #144. Same comment as 69e1973 re needing to update "replaced in" spec version before merging integration branch into `main` applies here too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What wins in this case — that specified by
RSC7aor that specified by the user?The text was updated successfully, but these errors were encountered: