fix: FilesViewerLoading was imported from a file that did not export it #3239
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.
ça ne posait pas de souci avec un usage classique de l'app : chargement de la home, puis navigation dans les dossier/fichier. Car la requête de récupération des fichiers est exécuté au lancement de l'app, et donc la navigation se fait sur le cache. Usequery dans les composants retourne alors toujours un tableau et non un null. On ne passe donc jamais dans le FilesViewerLoading.
Sauf qu'avec un refresh sur la visualisation d'un fichier, la query est réinitialisée, donc on passe par un null, donc l'app plantait car l'import n'était pas bon.