Skip to content
This repository has been archived by the owner on Nov 12, 2019. It is now read-only.

compatibility with listClients API #518

Merged
merged 2 commits into from
Apr 10, 2018

Conversation

tuhina2020
Copy link
Contributor

@tuhina2020 tuhina2020 commented Apr 9, 2018

@eliperelman
Copy link
Contributor

From reading the associated auth PR, it looks like during the transition to the new API, it will switch from returning the clients in an array to returning the array at the clients property in an object. Am I understanding this correctly?

When the API switches to have a continuationToken, do we foresee any breakage from the introduction of this?

cc: @djmitche

@djmitche
Copy link
Contributor

djmitche commented Apr 9, 2018

Yes, that's precisely the idea. It's a breaking change, and the point of this PR is to make tools work both with the old and new response bodies.

const clientResponse = await this.props.auth.listClients(
clientPrefix ? { prefix: clientPrefix } : null
);
const clients =
Copy link
Contributor

Choose a reason for hiding this comment

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

It might be good to put a comment in here pointing to the bug.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added a relevant message to the listClients API call

@eliperelman
Copy link
Contributor

Thanks for your work here @tuhina2020!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants