ui: Replaces destroyRecord with unloadRecord for KV 404's (#5837)
Just because Consul gives us a 404 this doesn't guarantee the KV doesn't exist, it doesn't even mean we don't have access to it. Furthermore we should never destroyRecord's without user interaction (therefore only via the repo.delete method). This switches destroyRecord to unloadRecord which performs the additional legwork to keep ember-data in sync with the actual truth. unloadRecord unloads the record from ember-data rather than sending an API delete request, which would have been the intent here.
This commit is contained in:
parent
52b71aaf96
commit
9999ccf503
|
@ -59,7 +59,7 @@ export default RepositoryService.extend({
|
||||||
const id = JSON.stringify([dc, key]);
|
const id = JSON.stringify([dc, key]);
|
||||||
const record = get(this, 'store').peekRecord(this.getModelName(), id);
|
const record = get(this, 'store').peekRecord(this.getModelName(), id);
|
||||||
if (record) {
|
if (record) {
|
||||||
record.destroyRecord();
|
record.unloadRecord();
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
throw e;
|
throw e;
|
||||||
|
|
Loading…
Reference in New Issue