consul/ui-v2/app/services/repository
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
..
nspace ui: Move routes to use data-sources (#8321) 2020-07-17 14:42:45 +01:00
type 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
acl.js
coordinate.js ui: Move routes to use data-sources (#8321) 2020-07-17 14:42:45 +01:00
dc.js ui: Move dc sorting to the view/template (#8297) 2020-07-13 14:22:58 +01:00
discovery-chain.js ui: Better error message checking for cross dc connect check (#8320) 2020-07-16 18:27:34 +01:00
intention.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
kv.js
node.js ui: Move dc sorting to the view/template (#8297) 2020-07-13 14:22:58 +01:00
nspace.js ui: Move routes to use data-sources (#8321) 2020-07-17 14:42:45 +01:00
oidc-provider.js
policy.js
proxy.js ui: Move routes to use data-sources (#8321) 2020-07-17 14:42:45 +01:00
role.js
service.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
session.js ui: Move routes to use data-sources (#8321) 2020-07-17 14:42:45 +01:00
token.js