Sawyer X

## Why? Just like the `plugin_setting` keyword in plugins, this is also a keyword from the old plugins interface. There is no need for this keyword since the new plugins...

## Why? Just like the `plugin_setting` keyword in plugins, this is also a keyword from the old plugins interface. There is no need for this keyword since the new plugins...

## Why? Just like the `plugin_setting` keyword in plugins, this is also a keyword from the old plugins interface. There is no need for this keyword since the new plugins...

## Why? `plugin_setting` is a keyword from the older implementation of plugins. Making it works required jumping through hoops we still cannot decipher even though we wrote them. There is...

## Why? Originally, `request->path()` (which is the `path()` method on `Dancer2::Core::Request`) had a broken implementation. We created the method `dispatch_path()` (which you could call as `request->dispatch_path()`). Since then, we fixed...

## Why? This keyword had a generic name while only being relevant to the response. ## Benefits to Dancer2 codebase More consistency and clarity in the code-base. ## Benefit to...

## Why? This keyword had a generic name while only being relevant to the response. ## Benefits to Dancer2 codebase More consistency and clarity in the code-base. ## Benefit to...

## Why? This keyword had a generic name while only being relevant to the response. ## Benefits to Dancer2 codebase More consistency and clarity in the code-base. ## Benefit to...

## Why? This is an older keyword reflecting the history in which there was a context object. This object has been removed since in favor of `Dancer2::Core::App` holding the context....

## Why? The storage that contains parameters has two special keys: `splat` and `capture`. If you create a named placeholder using one of those names, it confuses the internal system,...