feat: Introduce route Skipper #4
Conversation
|
@thzois I'm guessing this is unmaintained at this point |
|
This would be nice to have in, perhaps @brpaz can have a look? |
Since the forked repo appeared to be unmaintained, we are pulling this open PR in: brpaz#4 Signed-off-by: Valério Valério <[email protected]>
|
This would be very usefull |
|
It is ashamed that this feature are yet to be introduced to the main release. Open source development is understandably can be time consuming without probable material gain and we can hardly blame contributors for not that active in maintaining the releases. I too actively using this middleware for logging my echo instances. If it is not too much to ask can I volunteer my spare times to help maintaining this repo @brpaz? |
|
Apologies for the late response, I thought this repository was unmaintained! @salleh did you merge this PR? Can we close it? |
I've merged the changes into my own fork. Not to this source repo. I've also added my own enhancement to the package there and propose that to be merged here as you can see in the other pull request. |
Hello!
Thank you very much for providing this middleware to the community :) We have been actively using it in our company, but we noticed that for health probes it constantly produces logs that we are not interested in. This PR introduces a Skipper, so that someone can decide to exclude certain routes from getting logged when a request arrives.
I have added the related tests and in order to be backwards compatible with the previous version of the middleware, I have added a default configuration.