Gaspard proposed improvements to the API for managing user permissions more efficiently.
Discussion on whether to update permissions individually or in bulk, with suggestions for new endpoints to streamline the process.
Conflict Management in Data Updates
@All
Participants discussed the need for a locking mechanism to prevent data conflicts during updates.
Concerns were raised about automatically refreshing data, with a preference for notifying users of conflicts instead.
Agreement on the necessity of implementing a lock mechanism across various entities in the project.
Discussion on whether to create a global class for the lock mechanism to apply to all entities.
01:00:00
Data Freshness and Real-Time Updates
@All
Discussion on ensuring data freshness in the front end and backend.
Proposal for implementing real-time updates to keep users informed of changes without manual refresh.
Acknowledgment of the complexity and workload involved in implementing such features.
01:05:00
Permission Management and Dependencies
@All
Concerns raised about the dependency of permissions on one another.
Discussion on how to manage permissions effectively to avoid conflicts.
Mention of the need for a more structured approach to permission assignments.
01:40:00
User Creation and Password Management
@All
Debate on the security of password handling during user creation.
Agreement that passwords should not be sent in clear text and should be encrypted on the backend.
Discussion on the need for separate data transfer objects (DTOs) for user creation and retrieval to avoid exposing sensitive information.
01:50:00
User Controller Refactoring Discussion
@All
Discussion on the need to extract a group's controller from the user controller.
Steve Tsala mentioned the removal of response entities in favor of returning plain Java objects.
Concerns raised by Alessandro Domanico regarding the implications of this change, especially in terms of error handling and consistency across controllers.