What kind of change does this PR introduce? (check at least one)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Feature (non-breaking change which adds functionality)
[ ] Code style update
[x] Refactor (refactoring or adding test which isn't a fix or add a feature)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Build-related changes
[ ] Other, please describe:
Does this PR introduce a breaking change? (check one)
[x] Yes
[ ] No
Did you test your solution?
[ ] I lightly tested it in one browser
[x] I deeply tested it in several browsers
[ ] I wrote tests around it (unit tests, integration tests, E2E tests)
Problem Description
Preloader component was always rendered in the App. We had some dummy assets loaded but if preloading assets list was empty you'd never see the site. In this flow devs had to clean up code by removing the Preloader and all its related logic from the app when they didn't need it.
Solution Description
Preloader will show up and perform loading only if assets list is not empty
removed dummy assets from the list
made sure to lazy load Preloader component only if there are assets to be downloaded
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Did you test your solution?
Problem Description
Preloader component was always rendered in the App. We had some dummy assets loaded but if preloading assets list was empty you'd never see the site. In this flow devs had to clean up code by removing the Preloader and all its related logic from the app when they didn't need it.
Solution Description
Preloader will show up and perform loading only if assets list is not empty
Side Effects, Risks, Impact
Aditional comments: