Dirk Van Haerenborgh

@owilliams320 Thanks for the reply. I realize that it can indeed work that way. However, we're then completely missing out on the tree-shaking capabilities, which would be quite sad.

I'll create an issue with them then. What package type would it need to be?

@JoshSchoen I mentioned in the gitter channel that I'd be willing to contribute, yes.

With transitive imports, I'm assuming you mean that i.e. PolicyC cannot import "end-user" from policyB (because that was imported by policyB itself)? So essentially, we can only construct policies 1...

Yes, indeed. #298 would make this situation possible, but it has some drawbacks, too. What we're proposing here would mean breaking the current API: a Thing would really just take...

Oh, that'd be very cool! Thanks! Even if you don't have time to rebase it right now, I'm very interested to see where you ended up.

I forgot to update the payload after I added the policy id as a pathparam :) I was pondering with the idea of not requiring any id in request url,...

By default, just including that library just adds support but does nothing more. You need the environment variable or an entry the application settings to change the default logging format...

I assume this would allow swapping tokios event loop with, for instance, glib?

Woops, I've been very busy the past few months. I'll look into it :) You're correct that this is something the ```MessageOwner``` is supposed to prevent. The notmuch docs are...