Jim Anderson

Thanks @eddumelendez! Also apologies for the extended delay here 😞. I love this change, and its a structure I had originally envisioned, but I wonder if it will run into...

:wave: hi @xXAvoraXx, thanks for raising an issue! If I am understanding correctly, you are expecting that the tuple arguments for write and delete are the same. However, the schema...

> Can we compromise on having different types of options per method? E.g. ReadUsersetTuplesOption, ReadChangesOption etc? I.e. fine-grained options 😄 Yes, I think that is a good idea as @rhamzeh...

Thanks @piotrooo! This is a good and well thought-out list! I don't have much to add to @rhamzeh's thoughtful response. I generally like AssertJ and WireMock but echo @rhamzeh's points...

Thanks for raising @flex-seongbok! Can you provide a bit more context about the issues you are having and how the ability to customize the executor would help? We currently have...

Hi @Lin064, thanks for providing detailed info! I am unable to reproduce this with version 0.9.1 of the java SDK. I have the following model: ```yaml model schema 1.1 type...

Hi @Lin064 I just ran this [this test app](https://gist.github.com/jimmyjames/24a2c4526610e9f0b7472ae602e8ea85) with v0.8.1 of the Java SDK and get the same results (list users returning user:1 and user:2 for viewer of folder:3)....

Hi @Lin064, I updated my store with your updated model and the tuples you recently shared. I see the same results as you, and to the point of this issue,...

Few questions in addition to coderabbit's: - it looks like we are only returning the first error and ignoring subsequent errors? - looks like it's only returning the first response?...

Thanks for the report @Milena92! Yes, this is an issue in this and other typed SDKs unfortunately. The problem is that in certain cases (like you described, to unset a...