Stop passing the WebEvent parameter, so it can be used generally #621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
The Web Event object is the first parameter supplied to the ScriptBlocks of Routes, Middleware, and Endware. These already all have access to the main
$WebEvent
object, including Authentication, without the need to supply it as a parameter.Therefore, to help keep code shorter/cleaner, the event should stop being supplied as the first parameter, and instead documented to just be accessed via
$WebEvent
.This change applies to Routes, Middleware, Endware, and Authentication. (Also the the
$SmtpEvent
when using the SMTP Server)Related Issue
Resolves #618
Examples
So from the following:
To this: