klesh commented on issue #2078: URL: https://github.com/apache/incubator-devlake/issues/2078#issuecomment-1346030056
> @klesh I was thinking, how about we put everything go-related under a broader "go" directory as well? Since config-ui contains all frontend related logic, I think a dedicated folder for backend will also help with the organization. It also makes more since as we are using a top-level python/ directory as well in the Python SDK branch. So something like go-backend/ which contains all the modules/packages, the go.mod/sum etc. Maybe py-backend in that other branch for python stuff. Good thinking, I would like to share my 2cents as well: 1. both go/python belongs to the Backend, while `go` acting as the dominating role controlling the whole operation and `python` serving as a optional helper for plugins, it makes more sense to put `python` inside the folder containing our `go` code. 2. should we keep the backend/frontend code inside the same repo? there were discussion talking about extracting config-ui to another repo. It is big, let's do it step by step, finish the go module relocation first. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
