Simon André
Simon André
```php parent::__construct($name, $template, null, true, 'attributes', false, 'ux_data_table', 'post', UrlGeneratorInterface::ABSOLUTE_PATH); ``` I assume this is just for illustration purposes, as forcing `csrf: false` doesn’t seem like a great idea 😅...
> What would be the timeline for this? I'm hoping early 2025.. On my side, I have a lot of features i'd like to work on, and many "bug" reports...
Not sure it would be a solution viable for the entire "symfony stack", but in UX packages, i think a lazy load of the CSRF would not be too hard...
@gremo thank you for reporting this! Could you open a new issue please with ideally a small reproducer ?
Ok i'm closing this issue for now, and you create a new one when you have those emails again, ok for you ? (it's easier for us to maintain /...
But data-poll should not use CSRF for me .. or you are talking about the action ?
What does the expection say ? In the end i'm not surprised as it's not valid HTML syntax. But if we can improve this let's do it :)
Do we accept "dashes" in the component names ? Maybe we could say if "`x-...:`" it is not a nested param ?
I don't think we will change the nested contract. But, i checked, you cannot create a blog `foo-bar`, so i really think we could change the nested regex to consider...
@kbond would that be ok for you ?