What is the standard way of avoiding duplicate per...
# talk-keto
l
What is the standard way of avoiding duplicate permissions/relations from being written in Keto? Both the http api and the gRPC client in node.js don't throw an error or seem to have any config to prevent this. Multiple permissions are causing an issue for me too. If I happen to reset my backend server, the next time the user account is created itll store the permissions, duplicating them if they existed before. This then casues a snapshot token not implemented issue the next time the permission is checked. Edit: seems to be tracked here, although no updates in since last October
👀 1