Closed troyel closed 6 years ago
@troyel I think this is a cache issue. I already saw this, try to give it a try in incognito mode and let us know
@troyel any update on this? Can you confirm this is actually a bug?
@adrianq seems to be good now. Regarding cache - is there any way we can force browsers to flush the cache when opening the app for the first time? I foresee some issues here when we deploy and many people will load the pages with the old JS code and not our fancy new one. Perhaps we can implement a test that if the JS is not of the correct versioning according to the app specs it will give a message and instructions to clear cache?
seems to be good now.
Cool!
Perhaps we can implement a test that if the JS is not of the correct versioning
The caching problem does not affect the custom JS code (as far as we have seen, it always loads the newest version). The problem lies with the HTML of the datasets that data-entry caches. We'll check if there is a workaround for this.
Created a dataset with all indicators in. This has forced forward some errors: