So, I opened a .js file of a perfectly fine working extension and all I did was changing the color hex code from green to red for a particular element. This change is not reflected on the screen when testing with Qlik Sense on my computer (still green element). But if I copy the extension to someone else computer (who never had the extension in the first place), then the change is shown (red element).
So I guess that Qlik Sense kind of caches the initial settings and that's why I am still seeing the previous color?
I tried the following:
- closing + reopening qlik sense
- removed the whole extension folder + shut down + copied it back
- tried the above in a new Sense app...
I ran out of ideas what else I could do...and I guess its something simple that every web-dev would know instantly
For decision changes to the file .js in the extensions folder had to rename the main file extension .js (in my case is the same file .js) and of the same name file .qext. It helped me. Probably this is due to the use of the cache memory in the platform Qlik Sense.
This is due to caching by the web browser, which is normal behaviour to prevent unnecessary reloading of the .js file - which can be awkward when performing development. As this is normal browser behaviour you may find information on how to suppress the cache and force a reload by Googling these terms.
The caches are only cleared automatically by web browsers when you close all the instances of the browser, which will include closing Sense. For occasional changes to the extensions, that may be OK, but it is inconvenient at least.
Although I am not sure whether these will work with the browser in QS desktop...
Logic will get you from a to b. Imagination will take you everywhere. - A Einstein