xaxys / maintainman Goto Github PK

We should support webp format in image hosting service.

Many API haven't be tested as well as many non-embed components adapter (e.g. s3 storage). They need to be tested as soon as possible.

It's a discussion. Currently, MaintainMan allow item count be negative, for the administrator may forget to add incoming records after purchasing. This make them be able to add missing incoming records after the item count be negative. Or the system can be blocked by not enough item and it can be a heavy load of work to re-add those consuming record for repairers.

Now our API follow RESTful standards. But encoutered with some problem that we can not easily recognize bussiness error and system error. Should we separate business errors from system errors, and return 200 with status: false for business errors? Or change the return content to make it more compliant with the Restful API?

We should add i18n support for response message.

We should find a way to allow role order adjustment on create and update role to better organize inheritance relationship between roles.
Or should we find a better way to process inheritance map?

With code quantity increasing rapidly, we found some problem when organizing project packages. We should reorganize packages to find a way to make new function pluggable and can be easy access to the pther parts of system.