Tobias Kaupat

it can. See current version of the readme.

Hi, we are also looking into this. I'm very interested in Updates about the state of the implementation. Let me know when I can help somehow.

I think this should be part of the router. Else the router should at least provide the required information about response types etc. It's something very fundamental of CoAP that...

Well I run into the same issue, I like to get query params in `ngOnInit` but they are still blank. will also go with some delay now ...

Sorry, I did merge the update to 0.14.0 first. Can you please update the pull request to also include the latest restic version? I will then merge the PR.

I'm looking for some persistent queue, this implementation looks promising but the biggest fear is ending up with corrupt data and data loss due to failures. Maybe that's sine Motivation...

I need to check that later. Maybe I was missing it in earlier Versions and just missed when it was added. Actually I very like the inline syntax of chi....

Just missing: `func (mx *Mux) With(middlewares ...func(http.Handler) http.Handler) Router` Adding middleware inline is a quiet nice API. Better than wrapping functions in functions.

Need to find some time but I will if nobody else does before me :)

Same issue here. Edit: But it's working yet.