You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Define top level errors that represent common error categories
Inside domain/internal packages, canonicalize all package specific errors into those top level errors.
Domain packages should know how to canonicalize those top level errors into package-specific errors when necessary, like in the case of a grpc server
This is a suggestion, we can do some discovery around what would work best works for us given that, ideally, error handling between OpenFGA and Okta FGA is consistent. Whatever we do, we need team buy-in.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Describe the problem you'd like to have solved
Design concern in our codebase: if an API call bubbles up an error that isn't understood by our mapping layer (
openfga/pkg/server/errors/encoded_errors.go
Line 69 in ab0d835
See some occurrences of this problem:
Describe the ideal solution
A suggested pattern by folks at Okta is:
This is a suggestion, we can do some discovery around what would work best works for us given that, ideally, error handling between OpenFGA and Okta FGA is consistent. Whatever we do, we need team buy-in.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: