Skip to content

Navigating between routes containing Leva panels with a same-name field uses stale data #478

@about-hector

Description

@about-hector

Hello @dbismut ,

I'm encountering a problem that I'm pretty sure is easy to fix but my lack of experience is impeding me to.
I tried to read the code, go-to-definition for types etc but I just can't figure it out.

I have a /components route in my website,
every components/[slug] route might or might not include a Leva panel to play around with the component.

When I navigate between different routes, say I move from /components/1 to components/2, if the panels on both the pages include a field with the same name (say 'width') what happens is that I'll have the width of components/1 inside of /components/2's panel, and instead of being in the correct order the same name field is always at the top.

I am sorry for my dumbness but I really can't figure it out,
can you hint me in the right direction regarding why this is happening?

I'd be happy to contribute to the docs if needed,
please let me know if I can be of use for pmndrs :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions