24 May: Database Roles

Uncodie now can handle roles to manage the access to a collection or entry

New ✨

Role management

Uncodie now supports PostgreSQL, Hasura, and Auth0 roles, enhancing security and performance across applications. When a user logs in, the app automatically sends the user's role to the backend, which then adjusts security settings accordingly.

New Approach to Handling GraphQL Requests

From now on, you can manage application roles by synchronizing roles between Auth0 and Hasura. It is essential that the roles are identical so that when the user's Auth0 token, which includes the embedded roles, is obtained, Hasura can read these roles directly from the token.

Improved 💪🏼

Improvement in Property Handling for Instances

When configuring components with arrays, the path of the array was always passed as a prop. When copying an instance of a component and the component was configured as a component, it would always overwrite that component.

The solution was to improve the algorithm for obtaining props for the arrays and to rebuild the structure of the components by comparing the instance with its parent component.

Fixed 🔧

Fix setVariable action

When configuring a "setVariable" action, the compiler was failing.

This was due to a change with the quotation marks, and the compiler was not updated.

The solution was to update the setVariable action.

Fix select and navigate action

The bug appeared when configuring an action, script, or prototype in the parent instance; it always executed the first one configured.

The problem causing the bug was that the inherited event was not being called correctly.

To fix this, the solution considered not only the name of the component and the event but also the index number of the instance.

Error encountered while creating a React project from any source

When attempting to create a ReactJS project, an error occurred, preventing the project from being created and indicating a request failure.

Upon reviewing the system, it was identified that a service responsible for launching Hasura was not running, and a command that grants permissions to the database was not executing. This issue arose because the command was separated from the creation function and was not invoked during the project creation process.