-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thorough request object retrieval algorithm #45
Thorough request object retrieval algorithm #45
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The implementation looks really good, but it would be nice to have both cases tested and not only the baseline one we hade before (even though it is important to keep it as regression test)
I might need help with that, I'm not sure how to provide a dummy response to a HttpClient.get request |
fixed in commit 19b4614 |
I'm unhappy with the added dependency on |
how would you make an http request, without an http client? |
|
||
typealias RequestObjectCandidateRetriever = suspend (Url) -> List<String> | ||
|
||
private val HttpClient.asRequestObjectCandidateRetriever: RequestObjectCandidateRetriever |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imho as
as the prefix indicates a function, but this is a property
Why don't we leave that up to the client, i.e. the caller of our library, as it has been the case up until now? |
fixed in commit 03a0cdd |
Improved algorithm for retrieving AuthenticationResponseParameters as asked for in a-sit-plus/valera#61 (comment)