-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smart way to debug #12318
Comments
Hello, you can try |
@a1012112796 @zhoutt96 I think debug is a low efficient development and it's not recommand by golang team. The best practice is writing unit test and add logs. |
I'd appreciate a Something like https://github.com/markbates/refresh or https://github.com/cosmtrek/air. |
This leverages `air` to watch the backend files and trigger `make backend` automatically when they change. It seems to work rather well together with `watch-frontend`. Fixes: go-gitea#12318
* Add 'watch-backend' This leverages `air` to watch the backend files and trigger `make backend` automatically when they change. It seems to work rather well together with `watch-frontend`. Fixes: #12318 * rework docs to a new section for continuous build Co-authored-by: techknowlogick <techknowlogick@gitea.io>
[x]
):Description
Hi gitea team, sorry to bother.
I am creating this issue to ask is there any smart way for debugging?
For now, when I do a change in backend, I need to rebuild the project everytime.
thanks.
...
Screenshots
The text was updated successfully, but these errors were encountered: