Usage of scopes in sessions and auth, adding CurrentRequest

[msmakouz]

Q	A
Bugfix?	❌
Breaks BC?	❌
New feature?	✔️

Refactored AuthMiddleware and SessionMiddleware

The Spiral\Auth\Middleware\AuthMiddleware and Spiral\Session\Middleware\SessionMiddleware have been refactored. Now, instead of starting a scope and defining bindings in it, they add data to the request attributes.

CurrentRequest

Added Spiral\Http\CurrentRequest, which will be available in the container in the http scope and is intended for obtaining the current instance of Psr\Http\Message\ServerRequestInterface. In this scope, ServerRequestInterface can be changed using middleware. Using Spiral\Http\CurrentRequest, you can obtain the current request object. For example, in the next middleware, after the previous middleware has added some data to the attributes. In the http.request scope, Psr\Http\Message\ServerRequestInterface will be available as before.

Added exceptions

• Spiral\Auth\Exception\InvalidAuthContext - when a user tries to use Spiral\Auth\AuthContextInterface, but the request attribute lacks the necessary data, the exception message advises configuring Spiral\Auth\Middleware\AuthMiddleware.
• Spiral\Session\Exception\InvalidSessionContext - when a user tries to use Spiral\Session\SessionInterface, but the request attribute lacks the necessary data, the exception message advises configuring Spiral\Session\Middleware\SessionMiddleware.

Scope limited via attribute

• Spiral\Cookies\CookieQueue - http.request
• Spiral\Cookies\CookieManager - http.request
• Spiral\Filter\InputScope - http.request
• Spiral\Http\Request\InputManager - http.request
• Spiral\Session\Session - http
• Spiral\Session\SessionFactory - http

Scope limitation check is disabled by default. It will be enabled in version 4.0.

Marked as deprecated

• Spiral\Auth\AuthScope - in favor of using Spiral\Auth\AuthContextInterface directly.
• Spiral\Auth\TokenStorageScope - in favor of using Spiral\Auth\TokenStorageInterface directly.
• Spiral\Session\SessionScope - in favor of using Spiral\Session\SessionInterface directly.
• Spiral\SessionSectionScope - in favor of using method getSection from Spiral\Session\SessionInterface instead.

[codecov]

Codecov Report

Attention: Patch coverage is 99.38272% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 89.77%. Comparing base (9a2b173) to head (db49785).
Report is 22 commits behind head on feature/scopes.

Files	Patch %	Lines
...xception/Shared/InvalidContainerScopeException.php	83.33%	1 Missing ⚠️

Additional details and impacted files

@@                 Coverage Diff                  @@
##             feature/scopes    #1080      +/-   ##
====================================================
+ Coverage             89.60%   89.77%   +0.16%     
- Complexity             6354     6381      +27     
====================================================
  Files                   830      836       +6     
  Lines                 17956    18085     +129     
====================================================
+ Hits                  16089    16235     +146     
+ Misses                 1867     1850      -17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.