Intergrate Vuex into Front end #228
Comments
alonttal
added a commit
that referenced
this issue
Apr 3, 2018
- Created a new "configuration" dir to store all related configuration. Added a Register-Icon file under it to set up our own icons (moved the related code from main.js). - changed imports to use "import" instead of "require". Vuex: - Created vuex-store for global data management. - Now search apartments are managed with vuex. - Updated "Main.vue" "SearchSection.vue" & "SearchResults.vue" to use vuex. Fixes: - Added key to InterestedSection.vue v-for loop to remove the annoying warning that was shown when running Vue development environment. Issues: #228 #229
|
This is done and well in the new front-end design. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I started integrating Vuex into the front end for easier and better data management.
The idea is to use a single point of interest for data which is shared among various components.
It does not harm scalability since Vuex stores can be splitted into differnet modules.
It saves the need to listen to event or to send data ('props') for some cases, especially when the data need to be sended recusively to deeper component childs.
Of course not everything should be saved in the Vuex-store, but only this data that is shared globally.
For example: If a PriceTag component recieves the price as prop, Vuex should not be used.
On the contrast, after searching for apartments we save the apartments recieved from the server in the Vuex-store, thus allowing to return to the previous page while maintaining the apartments list.
Work done so far:
If you update anything related in the code remember to update everyone here & assign yourself to the issue.
The text was updated successfully, but these errors were encountered: