Vance Lucas

Yeah, I was initially thinking about implementing this as a call-time parsing, so if the `$request->user()` or `$request->password()` methods were called, THEN it would check for the `Authorization` header and...

Hmmm. There does seem to be room for a new feature here. Do you have any recommendations on syntax or exactly what you need? I'd definitely like to build something...

Maybe there just needs to be a way to tell Bullet the request is "done", and to send what's in the current response object?

Yes - it makes perfect sense - basically a way to shortcut out of the route parsing step from inside a route and just return the current response object as-is.

I think basically you just have to do: ``` php $response->send(); exit; ``` And you can achieve what you want. It's not terribly elegant, but it works.

This would require a major version bump (I am not opposed to this, just saying it will :)).

I think that would be a necessity for dropping support of previously supported PHP versions, yes.

Hhhmmm... what an unfortunate mistake. I think the user expectation is that `SpecificException` be handled first, and then fallback to a generic `Exception` handler. In practice, I do wonder how...

Seems like @netom should fix this in v2 :)

Unfortunately, the title doesn't say it all. Required with what? Another field? A specific value? Please elaborate. A specific use-case would be appreciated.