-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(core): remove middleware from actions #13262
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 0cf031e The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
fd88009
to
e285d9e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although this is a refactor, maybe should we have a changeset to be safe in case people face issues
b9ef104
to
bd84a49
Compare
CodSpeed Performance ReportMerging #13262 will not alter performanceComparing Summary
|
Turns out it is not as simple as that, it requires a full refactor of the architecture. I'll see to that |
bd84a49
to
64e2187
Compare
64e2187
to
c2042d2
Compare
I checked the e2e test that failed, and the issue isn't much clear. The db package fails to run the seed file, however it doesn't happen when I run the dev server for the fixture. Also, when running the fixture locally, the likes action (the action) works as expected, but the query doesn't return the expected data. This doesn't happen for the comments action. As for now, I commented on them. |
f47d495
to
0cf031e
Compare
Changes
This PR a start to make Action more "core aware". In this PR the use of the middleware is completely removed, and its logic is moved inside the
render-context.ts
render function, in particular thelastNext
, which is the last function that is called during the rendering phase.Testing
Current tests and functionality should stay the same. The Actions middleware was already set to be the last one, which is the same as we just moved inside the
lastNext
callback we have in core.Docs
N/A