You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that if I have nested components and the parent component is included with loading: 'defer', the child component can no longer read URL parameters. Here is my code:
Parent Component
<?phpnamespaceApp\Twig\Components;
useSymfony\UX\LiveComponent\Attribute\AsLiveComponent;
useSymfony\UX\LiveComponent\DefaultActionTrait;
#[AsLiveComponent]
class ParentComponent
{
use DefaultActionTrait;
}
If I now call up my page with ?sort=foo, the value “name” is dumped instead of “foo”. If I remove the { loading: 'defer' } from the parent component, the value “foo” is dumped. Is it possible in this scenario that the parent component remains defered and the child component can still read the URL parameters?
The text was updated successfully, but these errors were encountered:
I have noticed that if I have nested components and the parent component is included with
loading: 'defer'
, the child component can no longer read URL parameters. Here is my code:Parent Component
Child Component
Main template:
If I now call up my page with ?sort=foo, the value “name” is dumped instead of “foo”. If I remove the
{ loading: 'defer' }
from the parent component, the value “foo” is dumped. Is it possible in this scenario that the parent component remains defered and the child component can still read the URL parameters?The text was updated successfully, but these errors were encountered: