Skip to content

Explain the signature of FrameInterface#807

Merged
shadowhand merged 2 commits intomasterfrom
mnapoli-patch-1
Aug 18, 2016
Merged

Explain the signature of FrameInterface#807
shadowhand merged 2 commits intomasterfrom
mnapoli-patch-1

Conversation

@mnapoli
Copy link
Member

@mnapoli mnapoli commented Aug 17, 2016

already use a class that implements `__invoke()` for the `$next` argument with
a different signature: `$request` *and* `$response`. Using the same method name
has the potential to make PSR-15 completely incompatible with these existing
systems without major changes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd maybe rephrase this last sentence to:

By selecting a different method, PSR-15 may be implemented within existing systems in parallel with existing features, providing a migration path for these libraries and their consumers. In some cases, existing __invoke() implementations could even proxy to the method defined by PSR-15, or vice versa.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 updated

@pmjones
Copy link
Contributor

pmjones commented Aug 17, 2016

Let me know when you feel it's ready and I'll approve. (Or @shadowhand can, as it's his baby.)

@shadowhand
Copy link
Contributor

shadowhand commented Aug 18, 2016

👍

Approved with PullApprove

@shadowhand shadowhand merged commit 3f00c28 into master Aug 18, 2016
@shadowhand shadowhand deleted the mnapoli-patch-1 branch August 18, 2016 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants