consul/ui-v2/app/services
John Cowen 77b4d8f42a
ui: Use X-Range header as a signal as to whether to reconcile the ember-data store (#8384)
* ui: Use `X-Range` header/meta to decide whether to reconcile or not

Previously we used a `shouldReconcile` method in order to decide whether
a response should trigger a reconciliation of the frontend ember-data
'source of truth' or not. It's a lot nicer/clearer if this 'flag' can be set
alongside the HTTP request information, moreover we almost have the same
functionality in `If-Range`/`Partial Content` HTTP functionality.

Here we partly follow this HTTP semantics but use a custom `X-Range` header
instead.
2020-07-29 10:16:09 +02:00
..
client ui: Use X-Range header as a signal as to whether to reconcile the ember-data store (#8384) 2020-07-29 10:16:09 +02:00
clipboard
code-mirror
data-sink
data-source ui: Use X-Range header as a signal as to whether to reconcile the ember-data store (#8384) 2020-07-29 10:16:09 +02:00
repository ui: Use X-Range header as a signal as to whether to reconcile the ember-data store (#8384) 2020-07-29 10:16:09 +02:00
atob.js
btoa.js
data-structs.js
dom.js
encoder.js
env.js
feedback.js
form.js
lazy-proxy.js
logger.js
repository.js ui: Use X-Range header as a signal as to whether to reconcile the ember-data store (#8384) 2020-07-29 10:16:09 +02:00
search.js
settings.js
sort.js
state.js
store.js
ticker.js
timeout.js