HookyQR

Accepting an invite from a link trashes the current workspace too. If you forget to open a fresh window before clicking. 😢

``` .to.have.props(['first', 'second', 'third']) // ``` passes. Chai Enzyme should be able to be used to determine if the property (key) is passes, no matter what the value, without having...

I didn't change `props`. It currently has `all` semantics and matches on key presence, thus matching when the value is `undefined`. By all, I mean all _expected_ values, but _any_...

Specifically, the PR will allow ```javascript expect().to.have.prop('third') ``` to have equivalent results to ```javascript expect().to.have.props(['third']) ``` No matter what the value of `props.third` actually is.

Additionally, (just noticed this) if you have `ss10` **off**, but `cv05` **on**, `fi` renders as though `cv05` is not set. I would assume solving the ss10 variants per @Adiraj18's request...

`compress.cascade` is no longer supported and `output.bracketize` has been replaced by `output.braces`. There's code in the extension to handle this, but I dropped the `e` out of bracketize, so it...

Should be fixed now. There's a second update required. (oops)

:warning: Make sure to **attach** this file from your *home*-directory: `/Users/brentonpahl/HookyQR.beautify-unresponsive.cpuprofile.txt` :warning:

You can use either `"brace_style": "none,preserve-inline"` or `"brace_style": "expand,preserve-inline"` to get that result, but it will obviously affect other parts of your code.

That's because the code itself is invalid. It should have either `routes =` or the whole thing should be surrounded by a curly brace pair. The parser simply thinks it's...