Skip to content

Conversation

@bwaidelich
Copy link
Member

Using singleton route part handlers can have severe side effects because they are shared between all route instances.

This change leads to an exception being thrown if a singleton handler is configured

Related: neos/neos-development-collection#5571

Using singleton route part handlers can have severe side effects because they are shared between all route instances.

This change leads to an exception being thrown if a singleton handler is configured

Related: neos/neos-development-collection#5571
@bwaidelich
Copy link
Member Author

DISCLAIMER: I changed this code in the browser, didn't test it yet!

Copy link
Member

@kitsunet kitsunet left a comment

Choose a reason for hiding this comment

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

I guess that's fine... Haven't tested but should work.
If you need a shared runtime cache that can always be a singleton you inject into the handler or so...

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.

2 participants