You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Since server-side paging is supposed to be used, queries that loads all database entries into the VUEX store must be removed. Otherwise the server side paging is pointless.
all those typescript files can be removed, if the loading into the store is not needed.
It should be considered, which data is needed initially at the start of the application (e.g. data for dashboard), these can/should be loaded into the store as usual.
as a reference store/index shows the listed store values
and the store/state-type represents the states of values saved in store
for the selection lists in drop-down menus the implementation of a suitable component should be taken into account.
The text was updated successfully, but these errors were encountered:
DritonGoxhufi
changed the title
Server-side loading eliminates the need for store dispatches
Server-side paging eliminates the need for store dispatches
Aug 23, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since server-side paging is supposed to be used, queries that loads all database entries into the VUEX store must be removed. Otherwise the server side paging is pointless.
It should be considered, which data is needed initially at the start of the application (e.g. data for dashboard), these can/should be loaded into the store as usual.
as a reference store/index shows the listed store values
and the store/state-type represents the states of values saved in store
for the selection lists in drop-down menus the implementation of a suitable component should be taken into account.
The text was updated successfully, but these errors were encountered: