consul/ui-v2/app/serializers
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
..
acl.js
application.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
coordinate.js
dc.js ui: Improved main navigation (#7673) 2020-05-12 17:14:28 +00:00
discovery-chain.js ui: Discovery Chain (#6746) 2019-12-18 12:26:47 +00:00
http.js
intention.js ui: Namespace Support (#6639) 2019-12-18 12:26:47 +00:00
kv.js ui: Namespace Support (#6639) 2019-12-18 12:26:47 +00:00
node.js
nspace.js ui: Namespace Support (#6639) 2019-12-18 12:26:47 +00:00
oidc-provider.js ui: Model Layer for SSO Support (#7771) 2020-05-12 17:14:41 +00:00
policy.js
proxy.js
role.js
service.js ui: Namespace Support (#6639) 2019-12-18 12:26:47 +00:00
session.js
token.js ui: Model Layer for SSO Support (#7771) 2020-05-12 17:14:41 +00:00