Jim Anderson

I agree with @poovamraj we should at least update the documentation to ensure its clear. And if we can add async support in a nice way, that's something we can...

Thanks for raising this and providing a test case! @pstojek and @salami if you're able to try out #153 and verify it resolves the issue that would be great! 👍

Thanks for the issue and context @scarter93! One thing we need to think about is how the domain objects represents both request _and_ response payloads. So when considering equality, how...

@scarter93 using jsonviews is an interesting idea. Another alternative would be to break out separate classes specific to their operation (e.g., `UserRequest` and `UserResponse`). Either would be a pretty extensive...

At this time implementing as the client objects are used as serialization objects for the request and response, implementing `hashCode` and `equals` isn't something we can do without introducing additional...

👋 Hi @pelletier197, thanks for the PR. I looked at the schema of the tenants API, and the `session_lifetime` and `idle_session_lifetime` are defined as integers. When I tried updating the...

Thanks @pelletier197, yes I see the same behavior you are reporting. It is confusing 😕 Sometimes the dashboard will use non-public APIs; that may be what's happening here. It is...

@poovamraj would you mind reviewing this PR while I'm out? As you can see from the conversation, there is a discrepancy between the API behavior and the dashboard UX. Given...

Hey @pelletier197, apologies for the delay while I was away. I'm going to look into this again this week and see if this change is something we can do, or...

Thanks for the details @scarter93. I don't think we can change the field to be a primitive type, as when serializing the object we don't serialize null fields. If we...