Zlatko Knezevic

@brechtm I assume you would be open to reviewing PRs that fix issues and/or add new things? Not sure, of course, I will have time, but I may need a...

@Xunius I tried to use it but it gave me some weird issues with the templates and because I was in a rush I just used the `citeproc-js` implementation. I...

I would say, from my perspective, that we should use these two streams as they've been designed, that is: * Operational output goes to STDOUT * Errors and similar go...

@piotrpMSFT http://www.jstorimer.com/blogs/workingwithcode/7766119-when-to-use-stderr-instead-of-stdout is a pretty nice explanation. TL;DR: STDERR is for diagnostic messages, while STDOUT is for normal app output. Since they are separated, they can be redirected independently, which...

@lepture I think I figured out what is wrong, and managed to unblock myself, however, there could be a more sinister issue in there. The docs @ https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc give all...

@lepture thanks for the fix!

Following this sample, I think that a bunch of stuff in there is actually around parsing the incoming request. So, when I got the endpoint up and running in Giraffe,...

This still exists. Is there an event that we could handle to grab what we need from a list of objects?

Don't work late nights, I guess. `!important` rule also works as a workaround. However, the bug is still there.

+1 here as well for docs change, though porting over `removeRoute` to 3.5 would also be welcome.