[WARP Telemetry] Work around platform issues

Work around issues in platform which manifest as bugs or
latency issues when attempting to visualize telemetry
from the WARP Server. Specifically:

* Handle the possibility that there is no matching
  representation for an object from EditRepresenter.
* Don't attempt to look up colon-separated domain object
  identifiers from persistence. This is a workaround to
  avoid latency issues from excessive persistence calls;
  filed WTD-659 to improve this solution.

Changes made to support resolution of WTD-644.
This commit is contained in:
Victor Woeltjen 2015-01-09 16:16:58 -08:00
parent f9a4ac548c
commit 782edfc3b7
2 changed files with 4 additions and 2 deletions

View File

@ -73,7 +73,7 @@ define(
// Handle a specific representation of a specific domain object
function represent(representation, representedObject) {
// Track the key, to know which view configuration to save to.
key = representation.key;
key = (representation || {}).key;
// Track the represented object
domainObject = representedObject;

View File

@ -21,7 +21,9 @@ define(
*/
function PersistedModelProvider(persistenceService, $q, SPACE) {
function promiseModels(ids) {
return $q.all(ids.map(function (id) {
return $q.all(ids.filter(function (id) {
return id.indexOf(":") === -1;
}).map(function (id) {
return persistenceService.readObject(SPACE, id);
})).then(function (models) {
var result = {};