Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proof-of-concept to see what migrating to Vue might look like.
It just implements a single small component (one volunteer post on the group volunteer page). This replaces the existing
one.html
template withone.vue
component.I created
Iznik.VueView
base class for backbone views that will render a Vue component. This should allow seamless migrations as you can replace one component at a time, without touching the rest of the page.The idea would be to then implement bigger and bigger components that use the smaller ones, slowly removing the backbone controllers and views as it goes up the view hierarchy.
This PR does not address how to handle data fetching/refreshing/actions inside Vue components, it just delegates to the existing backbone controllers for that. Vue events are mapped to backbone view actions so it works in a similar way to the existing backbone views.
There are many approaches to state management in Vue, and some would involve much bigger changes (e.g. centralized state management like Vuex), other solutions would be more similar to the current setup (e.g. actions/lifecycle events in the vue components to do data fetching).