Read and write using different tuple models

Checklist

• I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved

I added the SDK to our backend yesterday and found that there are two different models being used when reading from the store and writing to the store.

from openfga_sdk import ReadRequestTupleKey, Tuple as FgaTuple
from openfga_sdk.client.models import ClientTuple

What's the reason for this? It would just save us some code to convert between them and make things cleaner with a single model/source of truth in the backend.

Thanks!

Describe the ideal solution

Read and write uses the same model for tuples

Alternatives and current workarounds

Cast in between them when reading, altering, and writing back to the store.

References

No response

Additional context

No response

Inizia tracciando le definizioni e gli utilizzi di ReadRequestTupleKey, FgaTuple e ClientTuple nell’SDK, quindi confronta i percorsi delle richieste di lettura e scrittura. Il lavoro è completato quando entrambi i percorsi usano un unico modello di tupla e i chiamanti non devono più eseguire il cast tra di essi.