Blake Embrey

Just realised that markdown doesn't support this, maybe replace with ``?

Here’s a previous issue related too: https://github.com/blakeembrey/free-style/issues/72.

So, my idea was that this code would minimise into literal strings (like code replacement). Is that how you both imagine it working too? It's actually pretty straightforward to do...

@cwmoo740 What do you think the value of keeping dynamic code paths around is? I would have imagined that if you're going to try and make it output CSS -...

> I think there are a couple things that would be good to discuss with the collaborators Do we have an open discussion around the use of magic strings already?...

@dougwilson I would be interested in maintaining them, if that sounds reasonable. Edit: I'll be working on some related type testing tools in https://github.com/typings/typings which will complement any such support...

Fantastic, I'll work on making sure the CI step is solved properly this week.

@LinusU Mutations are hard to represent in TypeScript, especially with things like adding a field during middleware execution. It's possible to merge the interfaces and we should do that, if...

@dougwilson Just FYI, all these issues are fixed on latest `path-to-regexp` (I fixed it last July) and should be possible to backport. Also, in the latest `path-to-regexp` you no longer...

@dougwilson Just wanted to clarify the previous message. It's actually _all_ provided out of the box with the latest `path-to-regexp` version and those changes could be back-ported (maybe some odd...