Echo JS 0.11.0

<~>

Citrus comments

Citrus 684 days ago. link 2 points
I've never used an out-of-the-box style guide.  I always work out with my team what style we want to stick with.  It's been different for every team, but it's never been bad.
Citrus 689 days ago. link 2 points
I would avoid bootstrap if you can.

Flexbox gives you the ability to do what one previously used boostrap's grid system for, and there are independently-built, react-friendly widgets that cover most of what bootstrap does.

If you must use a framework, I'd suggest using Semantic UI instead.  It's more "react-friendly" out of the box.
Citrus 767 days ago. link 2 points
It sounds like you're in the territory where using Typescript might provide you some tangible benefit.  That may be the least amount of extra typing into your code that you can get away with, and have the system stop you if there's a type mismatch.

The cost of that is a transpilation step.  Whether that's worth it, or even a good idea, is up to you.
Citrus 1055 days ago. link 2 points
Much of the time, I've found that we want the more-specified routes to match first, leaving the more generally specified routes to only match if there isn't one more specifically specified.

In other words, no matter where the route is registered, the second route should always match if it can, and the first should only route if the second can't.

As for your initial question, I would say that you could go either way, as long as the library is consistent about the behavior, and that behavior is clearly documented up front.  That said, what you're suggesting makes sense.  Just make sure your documentation is very clear that that is the effect.

"Explicit is better than implicit."  At least when it comes to routing...
Citrus 1103 days ago. link 1 point
"Magic comments" are pretty much universally bad.  Every programming language expects that code will function the same both with and without comments.

What you might consider, which would survive minification, is to use a large string literal instead.  A string, by itself on a line, is a valid JS statement (that doesn't do anything).  Which is why "use strict" works, even in environments that don't support it.
Citrus 1373 days ago. link 1 point
This all sounds like a disaster to me.  Am I the only person left who thinks that adding types to JS is a BAD thing?