-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
fix(files): sort not working after changing views #50161
base: master
Are you sure you want to change the base?
Conversation
/backport to stable30 |
/backport to stable29 |
Signed-off-by: Richard Steinmetz <[email protected]>
446823a
to
1c3ec2a
Compare
const actualNavigation = getNavigation() | ||
actualNavigation.addEventListener('update', () => { | ||
Vue.set(Navigation, 'views', actualNavigation.views) | ||
Vue.set(Navigation, 'active', actualNavigation.active) | ||
}) | ||
actualNavigation.addEventListener('updateActive', () => { | ||
Vue.set(Navigation, 'active', actualNavigation.active) | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should already be handled by the useNavigation
composable.
Seems like mixin/filesSorting.ts
is the last place that uses the $navigation
property directly.
Maybe just replace the usage of this.$navigation
then this whole object can be dropped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There already is a composable for this? I feel stupid now ...
I'll refactor the code then and get rid of the global prop.
Summary
Sorting the tabular view in files breaks if the view is changed twice.
Not a beautiful solution but it works ...
How to reproduce?
Problem: The global
$navigation
object is not reactive enough and misses some changes.Before
2025-01-14.13-49-24.mp4
After
2025-01-14.13-51-11.mp4
TODO
Checklist