Skip to content
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

Fix: development configuration for running the project is not vey intuitive #17

Open
6 of 10 tasks
pankajjs opened this issue Oct 23, 2024 · 0 comments · May be fixed by #20
Open
6 of 10 tasks

Fix: development configuration for running the project is not vey intuitive #17

pankajjs opened this issue Oct 23, 2024 · 0 comments · May be fixed by #20
Assignees

Comments

@pankajjs
Copy link

Issue Description

The current development configuration for running the project is not very intuitive.
For example in Makefile -

  1. air command does not convey its functionality. However it prints "Running the Go project using Air..." this message in console. Also, when we run air command it generates a tmp folder which contains the build of the project and it is not added in .gitignore file.
  2. It does not have build command to build the project.
  3. The run command builds and runs the project implicitly. However, It would be better if it builds the project and then runs it explicitly.

Expected Behavior

  1. Replace air command with dev in Make file
  2. Generate air.toml file to easily configure the project for live reloading
  3. Add the build folder in .gitignore
  4. Add build command
  5. Modify run command to explicitly build the project and run

Screenshots

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Check Makefile
  2. Execute command to cross check the issue

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant