-
Notifications
You must be signed in to change notification settings - Fork 5
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
Removing api router scope #32
base: master
Are you sure you want to change the base?
Conversation
…f healthcheck route
É necessário modificar incrementar uma nova versão no package.json |
return res | ||
.status(200) | ||
.json({ message: `Hello, I'm attiv and I'm here to help you develop software faster, robust and secure.` }); | ||
.json({ message: `Hello, I'm attiv and i'm here to help you develop software faster, robust and secure. The process is running for ${Math.floor(process.uptime()) / 60} minutes` }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's another "I'm" that can be replaced by "i'm".
Another suggestion is keep uptime in seconds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not better keep it in minutes? Why do you prefer in seconds?
I think the number in seconds will be too big if all the things are running ok, making dificult to human readability
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think is more common. With minutes we have the same problem when it's running for a long time, I think. Maybe add the startup time helps 🤔
@beeblebrox3 eu alterei conforme requisitado! |
@rlrezende @beeblebrox3 O que precisamos para mesclar este? |
Description
Other changes (e.g. bug fixes, UI tweaks, refactors)
Related Tickets
#31