Hello @carloscuesta :sunglasses:!
:stethoscope:
I already submitted PR #667 for this.
Hey @hf-kklein 馃憢 Thanks for the proposition.
What do you mean with the term healthchecks in programmation? 馃 Do you have an example for it?
What do you mean with the term healthchecks in programmation?
A health check is an endpoint used in Web APIs. It allows to easily check if a system is up and running, e.g. by testing if the database credentials are ok. See e.g.
I really like the concept behind the emoji! But I'm a little bit worried about the specificity of it
I'm personally not a huge fan of commits that you only use once in the project, and I don't see this being used more than once :thinking:
Thanks for your feedback!
But I'm a little bit worried about the specificity of it
I agree it's a very backendish thing.
and I don't see this being used more than once 馃
It's not uncommon to have multiple health checks or adding more checks over time. Usually there is one common endpoint, which is only created once; that's right. But there might actually be more than one check that is run when calling the health check endpoint. Think of, for example:
So I wouldn't say it's a "once a in project lifetime" commit emoji as basically a lot of features could come with their own health check that needs to be written and registered. For these commit emoji would imho be useful.
Most helpful comment
Thanks for your feedback!
I agree it's a very backendish thing.
It's not uncommon to have multiple health checks or adding more checks over time. Usually there is one common endpoint, which is only created once; that's right. But there might actually be more than one check that is run when calling the health check endpoint. Think of, for example:
So I wouldn't say it's a "once a in project lifetime" commit emoji as basically a lot of features could come with their own health check that needs to be written and registered. For these commit emoji would imho be useful.