Split MR widget into etag-cached and non-cached serializers
What does this MR do?
Splits auto-refreshing of MR widget into 2 requests:
- the one which uses etag-caching and invalidates the fields on change
- the one without caching
The idea is to gradually move all the fields to etag-cached endpoint
Related issue
Edited by Gary Holtz