Conversation
This patch provides * [x] initial documentation * [x] setup necessary for migration to a `mezzio/*` package * [x] basic integration testing with a full `mezzio/mezzio` skeleton-alike installation * [x] parsing of parsed BODY parameters and route parameters * [x] CI setup * [ ] parsing of QUERY parameters ( see CuyZ/Valinor#748 )
Should also fix: ``` Invalid workflow file: .github/workflows/continuous-integration.yml#L11 error parsing called workflow ".github/workflows/continuous-integration.yml" -> "laminas/workflow-continuous-integration/.github/workflows/continuous-integration.yml@1.43.0" : failed to fetch workflow: reference to workflow should be either a valid branch, tag, or commit ``` Ref: https://github.com/Roave/mezzio-valinor/actions/runs/22590162608
Most scaffolding of this component was copied from `laminas/laminas-session`, and here we are removing all the remaining references.
17f53ca to
4763b52
Compare
…tegrates with `laminas/laminas-servicemanager`
Fixes: ``` Error: docs/book/v1/intro.md:101:3 MD047/single-trailing-newline Files should end with a single newline character ``` Ref: https://github.com/mezzio/mezzio-valinor/actions/runs/22627736362/job/65568913920?pr=1#step:3:508
|
Well, I have no idea why the Backward Compatibility Check fails... Probably because |
This is a small and security-sensitive codebase: each branch **must** come with respective testing and examples.
|
I'll sign the commits before merge: don't want to rebase before doing that |
gsteel
left a comment
There was a problem hiding this comment.
LGTM! I don't have much to add…
Some kind of automatic mapping would be very attractive to users - ATM, we have that via a merged array, but no control over the merge order - maybe the user wants body to override route attributes for example.
Am I right in understanding that in CuyZ/Valinor#748 usage of Attributes such as #[FromRoute] is mandatory?
| return $next(array_merge( | ||
| $body, | ||
| $routeParameters, | ||
| )); |
There was a problem hiding this comment.
So the potential conflicts here will be solved by #2? i.e. users explicitly define where the data comes from by annotating the DTO with #FromRoute etc and using HttpRequest::fromPsr($request, $routeParamsExtractedFromReqAttribute) here?
That's pretty much what I'm toying around with in #2 :D |
This patch provides
mezzio/*packagemezzio/mezzioskeleton-alike installation