Robert Masen

> the user provided the wrong auth info, i.e. after a custom is_authenticated call I would expect this should lead to a 403 and not another 401 as defined [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#the_general_http_authentication_framework),...

> normally nobody notices that because they probably chain the `.with()` at the end of their route avoiding it by chance. So I guess the auth filter is implemented correctly,...

This feature was included with the v0.8.0 release

A note was added to the README.md as part of #75

I think skipping ahead and then skipping back is really the only way in this case. Thinking through this particular part of the grammar there is one more thing we...

One last nit: Can you squash the `fmt` commit into [Added tests for es2020 operators](https://github.com/rusty-ecma/RESS/pull/101/commits/4ff535d0f5f28f08666cd3b5c4d754cb57b2a474)? then I can merge it and publish the new version

The resast wouldn't get published, just a new alpha version of ress that can be consumed by ressa to generate the resast changes you are working on. sorry, the landscape...

At the very least the AST will always be tied to the lifetime of the js text used to parse construct the parser. The parser's lifetime is only there to...

Thank you for the bug report!

Is this something you would be interested in fixing?