2023-06-12 01:59:33 +02:00
|
|
|
### Consistency in error management
|
2023-06-11 21:10:03 +02:00
|
|
|
|
|
|
|
|
**Both exceptions and error reponses are used**.
|
|
|
|
|
A choice should be made between the two options.
|
|
|
|
|
A combinaison of both is fine as long as the logic is comprehensively documented.
|
|
|
|
|
|
|
|
|
|
**Response::Error** class is overused.
|
|
|
|
|
A simple error message is given instead of specific messages for each recurring error.
|
|
|
|
|
In the same time, some exceptions (such as **AdminAuthenticationException**) are used a few times for the same kind of errors.
|
|
|
|
|
|
2024-07-10 17:55:42 +02:00
|
|
|
### New features
|
|
|
|
|
|
|
|
|
|
- On login: inform the user he doesn't have an email address.
|
|
|
|
|
This happens when the user was migrated.
|
|
|
|
|
|
2023-06-11 21:10:03 +02:00
|
|
|
### Structures, not classes
|
|
|
|
|
|
|
|
|
|
Maybe in some cases, it could be great to use structures instead of classes.
|
|
|
|
|
They are simpler, use less memory and computation.
|
|
|
|
|
|
2023-06-12 01:59:33 +02:00
|
|
|
### CLI client
|
|
|
|
|
|
2024-12-11 11:34:45 +01:00
|
|
|
Current client **authctl** lacks most requests.
|
2023-06-12 01:59:33 +02:00
|
|
|
|
|
|
|
|
### Documentation
|
2023-06-11 21:10:03 +02:00
|
|
|
|
|
|
|
|
Documentation isn't started, yet. TODO!
|
