-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
[TwigComponent] Support HTTP render #707
Comments
I also think that TwigComponents is a great replacement for This is already possible today. What piece are you missing? You mentioned:
Can you give me more info about the use-case? If you transform a
|
Yes, you are right, but for setting
We do not use LiveComponent, since need a solution only for the backend without js. TwigComponent looks like a good analogue https://github.com/viewcomponent/view_component Perhaps it makes sense to move this feature to TwigComponent from LiveComponent. |
Thank you for this issue. |
Friendly reminder that this issue exists. If I don't hear anything I'll close this. |
Hey, I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen! |
TwigComponent
is great as a replacementrender(controller(...))
. The page often consists of different blocks, and in order not to overload the controller, the page could be broken throughrender(controller (...))
but he causes performance issues CPU.At the moment, the only difference is that the controller can be called on the URL. It is very common to need update a specific block after submitting form. What do you think about this?
The text was updated successfully, but these errors were encountered: