InfoMapper caching issues have mostly been resolved, as follows:
Application files are cache-busted by using Angular's approach of adding random characters to resources. The index.html file always seems to reload. CloudFront files are invalidated when uploaded.
Dataset files are now mostly managed as separate landing pages with CloudFront-hosted files. Files are invalidated when uploaded.
However, I have seen that uploading a new map configuration file may not result in the new map displaying, even if I verify that the file from the URL matches the local latest file. The map is updated in incognito (I think). Checking the Chrome Network file list shows the file being cached. This is an issue because new map configurations (and other data) need to be reflected in the application. This does not seem to be an issue when calling web services such as the NovaStar data or other data, although I may not be noticing everything. A page refresh or Ctrl-F5 did not resolve the issue.
Is the map configuration file loaded in a different way than other data? Any thoughts? I'll keep my eye on other map updates.
InfoMapper caching issues have mostly been resolved, as follows:
index.htmlfile always seems to reload. CloudFront files are invalidated when uploaded.However, I have seen that uploading a new map configuration file may not result in the new map displaying, even if I verify that the file from the URL matches the local latest file. The map is updated in incognito (I think). Checking the Chrome Network file list shows the file being cached. This is an issue because new map configurations (and other data) need to be reflected in the application. This does not seem to be an issue when calling web services such as the NovaStar data or other data, although I may not be noticing everything. A page refresh or Ctrl-F5 did not resolve the issue.
Is the map configuration file loaded in a different way than other data? Any thoughts? I'll keep my eye on other map updates.