Unify different technical terms - #880
Merged
Merged
Conversation
- Requests and responses are processed. - Middleware dispatchers dispatch middlewares.
schnittstabil
force-pushed
the
tweak-wording
branch
from
February 8, 2017 08:32
9500ca8 to
32ee7b1
Compare
Member
|
@php-fig/psr-15 |
Contributor
|
👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In my opinion, a standard should use as few technical terms as possible to not confuse implementers (this PR supersedes http-interop/http-middleware/pull/59).
It unifies different technical terms (process, handle, execute and dispatch):
process aligns with the method names and the wording introduced by @weierophinney at
middleware-meta.md(#878):dispatch aligns with the wording chosen at
middleware.md:@weierophinney I've replaced some of the wording you've recently introduced, please take a look.