Damien Lebrun

The doc only describes how to convert your firebase rules to bolt. How a bolt definition translate to firebase rules is an implementation detail. Does it matter that it uses...

@ilanbiala the recipes should be using the new API correctly. They might no show the best practices however. Maybe we're missing some recipe updates from master too.

@ddo Rebased on master

@ddo Define `parseUrl(url)` with the other helpers.

That's crud fix. Maybe we should parse the URL without reg. exp. It would avoid any breaking changes.

Based on https://en.wikipedia.org/wiki/URL (although I just notice the password part of the auth should be optional). The host is optional but required for OAuth request: ``` /^ (https?):\/\/ # scheme://...

Possibly. We don't need to extract the scheme + port and later the query with the same regexp.

I think `#`, `[` and `]` should be encoded in a query string; see RFC 3986 section 3: ``` unreserved = ALPHA / DIGIT / "-" / "." / "_"...

Note that URLSearchParams encode all reserved chars but `*`: ```js const qs = new URLSearchParams(); qs.set('sub-delims', "!$%'()*+,;="); qs.set('other', ":@"); console.assert(qs.toString() === "sub-delims=%21%24%25%27%28%29*%2B%2C%3B%3D&other=%3A%40") ``` It's not because they are valid that...

I personally run my tests with istanbul, then remap the "coverage-final.json" and finaly generate the reports with: ``` shell istanbul report lcov text ```