| We currently always cache the LiveTable results when using a LiveData with a LiveTable source: this is important for scalability but it's also very annoying when inserting a new LD when we're not entirely sure about the proper parameters to set.
In such situation it often happens to have to change a few times the parameters to test the results, and it's really providing a WTF effect on dev to always see same response, especially since it's difficult to debug the inner LiveTable request. Right now it's possible to workaround this by changing the ID of the LD but IMO It's not a good option as we generally start with the proper ID we'd like.
So I would propose the following changes:
1. to always provide in the LD result a boolean parameter indicating if the results is coming from a cache, so that when devs are checking the results they can immediately understand that it was cached (could be related to some headers also)
2. to allow provide a new metadata parameter to force disabling the cache in a specific LD (or provide a script service for that maybe) Ideally we would also need a better way to debug requests performed internally to the LT source but I don't have good ideas for that right now. |
