-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix list endpoints #236
Fix list endpoints #236
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.
Unrelated to the code here, but I noticed all the List*Options
classes have Jackson JSON annotations. Wondering if those are even useful or potentially just misleading and can be removed?
val params = | ||
(obj::class as KClass<T>).memberProperties.associate { prop: KProperty1<T, *> -> | ||
prop.name.toSnakeCase() to | ||
prop.get(obj)?.let { value -> | ||
if (value::class.isData) { | ||
toMap(value) | ||
} else { | ||
value.toString() | ||
} | ||
} | ||
} | ||
|
||
return params.filterValues { it != null } |
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.
Lovely ☕
To be honest, I have no idea why those annotations are in there. I'd rather not remove them though till we understand why there were put there in the first place. |
* User Management support (#212) * Add Beta SDKs section in README.md (#213) * Add Beta SDKs section in README.md * Nit/typo * Nit in section about Beta releases in the README.md (#214) * Nit in section about Beta releases in the README.md * Improvement to README.md * Update README.md * User Management support * Update version (#215) * Add Beta SDKs section in README.md (#213) * Add Beta SDKs section in README.md * Nit/typo * Nit in section about Beta releases in the README.md (#214) * Nit in section about Beta releases in the README.md * Improvement to README.md * Update README.md * Update version * Fix release script (Beta branch) (#217) * Add Beta SDKs section in README.md (#213) * Add Beta SDKs section in README.md * Nit/typo * Nit in section about Beta releases in the README.md (#214) * Nit in section about Beta releases in the README.md * Improvement to README.md * Update README.md * Fix typo in release script * Add organization membership events (#218) Add organization membership events. * Update beta version (#219) * Add events and API changes for invitations and Magic Auth (#221) * Add events and API changes for invitations and Magic Auth * Fix failing test * Rename event data * v3.1.0-beta.user-management3 (#222) * Add organization membership deactivate and reactivate API methods. (#226) * Bump to version 3.1.0-beta.user-management4. (#227) * Add methods and events for email verification and password reset (#228) * v3.1.0-beta.user-management5 (#229) * Add find invitation by token method (#230) * Fix list endpoints (#236) * Now correctly parsing data as params for GET requests * Value has to be a string * lol linting * 3.1.0-beta.user-management6 (#233) * `invitationCode` should be `invitationToken` (#237) --------- Co-authored-by: amadeo <165715960+amadeo-workos@users.noreply.github.com> Co-authored-by: Matt Dzwonczyk <9063128+mattgd@users.noreply.github.com> Co-authored-by: Blair Lunceford <74257063+blairlunceford@users.noreply.github.com> Co-authored-by: Michael Hadley <m@mthadley.com>
Description
Don't be fooled by the line count, it's mostly my editor fixing spacing issues.
data
gets passed into a request which is then used to form the request body. In the case of aGET
though there isn't a body, but there can be URL parameters. Data was being passed into list endpoints for UM, but because there is no body with aGET
it was being ignored.This fixes that by parsing
data
as a map and using it as URL parameters for list requests.Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.