[Q] React Role

[prime lake]

Hi @wintry stone, client side isn’t a suggested place to engage WriteDB. Main caveat is writing relation tuples in client side can cause inconsistency. We’re suggesting to doing write relations on db traction to ensure consistency.

If your application does not require up to date consistency especially on access control checks, then react role can be used to communicate with writeDB

[wintry stone]

@prime lake Yeah i should have clarified.

We don't plan on doing any direct database work from client-side for obvious security reasons but you are making it sound like there might be data consistency issues too trying to do so currently.

The front-end work is just one part of interfacing with the API side to ensuring we can enforce Permify's permissions.

That back-end API layer doesn't exist beyond permify-node from what I can tell which means we'd have to write all our api endpoints manually and map them one to one with Permify's endpoints (check, write, etc) to communicate with writeDB. Before we go down this route, I wanted to see if there was a simpler way to interface with the Permify API via the client.

Are there plans to make these work together more seamlessly and without data consistency issues? e.g) we'd pass say a Permify client instance to PermifyProvider and it'd interface more directly with the Permify API?

[wintry stone]

Maybe this ties into the product a bit too you plan on offering.

Are @sleek mirage/react-permify and @sleek mirage/react-role the same thing? If not, is react-permify what you plan on offering in your cloud portal and not opening sourcing it?

I'm trying to understand the business model here and what I need to implement myself versus what is available.

[prime lake]

Since we don't have REST client for nodeJS right now, all endpoints should be implemented manually as you mentioned. And unfortunately there is no simpler way of doing it right now. About the data consistency part actually I meant you'll be face potential inconsistencies if you directly call APIs from your react application. Moreover, there are no plans for making these (react-role with Permify instance/API)

[prime lake]

We deprecated the "@sleek mirage/react-permify" package, sorry about the confusion. We had a cloud package previously so it was the react client for that cloud service - which is not active today. We're fully open source right now - yet we have plans for cloud/hosted service for future.