the way our code is currently structured, to add a very basic piece of functionality requires writing/modifying code across three completely separate packages and understanding the (sometimes very confusing) ways they interact with each other. I've created some proof of concepts to demonstrate that we can contain all related code within the same package to make it a lot easier to work on a feature without context-switching. It also reduces the amount of boilerplate since most of the repetitive work is handled by the code generation.
files necessary to modify a user endpoint with the current code:
satellite/console/consoleweb/server.go
satellite/console/consoleweb/consoleapi/users.go
satellite/console/service.go
files necessary to modify a user endpoint with the structure I would like to migrate to:
We are going to close this roadmap issue until we get more customer feedback that this type of functionality would solve pain points they have. @NiaStorj @ferristocrat @mobyvb
Description
the way our code is currently structured, to add a very basic piece of functionality requires writing/modifying code across three completely separate packages and understanding the (sometimes very confusing) ways they interact with each other. I've created some proof of concepts to demonstrate that we can contain all related code within the same package to make it a lot easier to work on a feature without context-switching. It also reduces the amount of boilerplate since most of the repetitive work is handled by the code generation.
files necessary to modify a user endpoint with the current code: