ash-m
ash-m
### Feature Request | Q | A |------------ | ------ | New Feature | yes | BC Break | no #### Scenario / Use-case Any time you want the full...
The runtime/react instantiates an HttpServer for you which is where one would define middleware. Can we abstract this in a decent way? Maybe we can add an optional `$middlewares` argument...
# Summary - [ ] What does a `name` filter refer to? - [ ] Plural `tags` + `--help` make valid configuration values for `filter` options ambiguous (string only? array?)...
At the moment, this bundle implements the underlying library using JWTs. The authentication mechanism checks if a token is revoked through an `AccessTokenRepositoryInterface` and requires a `UserInterface` for the `doAuthenticate()`...
The current library wraps authorization middleware around a resource server. Some specifics on how this is configured by the bundle would help us implement an authorization flow for validating tokens...
Currently misleading: ``` paths Optional path(s) to execute. ``` Makes it seem like `paths` can be a list of arguments. It should really be: `Path to feature(s) to execute (optional).`
The docs for [`strcmp`](https://www.php.net/manual/en/function.strcmp.php#refsect1-function.strcmp-parameters) say: > ### Return Values [¶][1] > > Returns `-1` if `string1` is less than `string2`; `1` if `string1` is greater than `string2`, and `0` if...
# Summary - [ ] What does a `name` filter refer to? - [ ] Plural `tags` + `--help` make valid configuration values for `filter` options ambiguous (string only? array?)...