Skip to content

Conversation

@Sebobo
Copy link
Member

@Sebobo Sebobo commented Jun 12, 2025

This change makes sure that each route has its own handler instance and prevents accidental sharing of instance properties. An optimal solution wouldn't need the splitString as instance variable anymore, but this would require a change in Flow.

Resolves: #5571

@Sebobo Sebobo self-assigned this Jun 12, 2025
Copy link
Member

@bwaidelich bwaidelich left a comment

Choose a reason for hiding this comment

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

Makes sense to me – this was a proper foot gun..

I think Flow should be more picky about this => neos/flow-development-collection#3485

Copy link
Contributor

@dlubitz dlubitz left a comment

Choose a reason for hiding this comment

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

LGTM!

@dlubitz dlubitz merged commit b43161e into 9.0 Jun 12, 2025
14 checks passed
@dlubitz dlubitz deleted the bugfix/5571-splitstring-error branch June 12, 2025 19:14
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.

BUG: EventSourcedFrontendNodeRoutePartHandler wrongly reuses splitString of previous routes

4 participants