| import requests | |
| class User: | |
| """User class""" | |
| def __init__(self, **kwargs) -> None: | |
| for k, v in kwargs.items(): | |
| setattr(self, k, v) | |
| def __str__(self) -> str: |
A Pen by @Baskervilles on CodePen.
Plugins can read data from the database by calling /data/read using a POST method
Why a POST Method? So we have the problem of plugins wanting to query the database, the current implementation uses URL parameters to specify the filters, which has posed some limitations, exposes sensitive data and makes querying complex.
A POST method hides sensitive information. A POST method may have a body in which we can then specify, the following JSON object.
| // Error Codes for SignUp | |
| ERROR_OPERATION_NOT_ALLOWED` - Indicates that Anonymous accounts are not enabled. | |
| ERROR_WEAK_PASSWORD - If the password is not strong enough. | |
| ERROR_INVALID_EMAIL` - If the email address is malformed. | |
| ERROR_EMAIL_ALREADY_IN_USE - If the email is already in use by a different account. | |
| ERROR_INVALID_CREDENTIAL` - If the [email] address is malformed. | |
| // sending password reset email | |
| ERROR_INVALID_EMAIL` - If the [email] address is malformed. |
Pourquoi ce document ?
Parce qu'il y a des smells dans les repository
Pourquoi parler de smell ?
Certains projets ont des branches develop, d'autres pas. On utilise les tags avec jenkins, on a des commits peu clairs, on n'utilise pas toutes les fonctionnalités de github (PR, issues)
Pourquoi sont-ce des smells ?
La rigueur est primordiale pour conserver du code maintenable dans lequel on peut avoir confiance et dont on peut être fier.