Skip to content

Conversation

@crbelaus
Copy link
Contributor

The navbar does not have any independent status so it doesn't need to be a LiveComponent. Being a LiveComponent was actually problematic as it was not able to generate the proper dashboard path for linking.

I noticed this because I had a bunch of filters applied and wanted to clean them all by returning to the default dashboard path. Contrary to what I was expecting clicking the ErrorTracker button maintained the filters.

This happened because the @socket assign was different from the main page socket, as the navbar was a separate LiveComponent and thus used a separate process.

before

After this change, the link goes to the default dashboard path as expected.

after

The navbar does not have any independent status so it doesn't need to
be a LiveComponent. Being a LiveComponent was actually problematic as
it was not able to generate the proper dashboard path for linking.
@crbelaus crbelaus requested a review from odarriba August 18, 2024 08:25
@crbelaus crbelaus self-assigned this Aug 18, 2024
Copy link
Contributor

@odarriba odarriba left a comment

Choose a reason for hiding this comment

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

Awesome 🚀

@odarriba odarriba merged commit 439b6b2 into main Aug 19, 2024
@odarriba odarriba deleted the fix-navbar-link branch August 19, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants