8c8443390d
Ember Data requires the usage of unique ID to identify its records in the frontend, and we use a centralized function to do that for all records. There are occasions where it can't make an ID, usually this is a bug our side, but there are occasions where Consul might not be giving us the data needed to make an ID, for example if a Service comes down to us with a blank Name. Whilst this isn't a problem to be fixed in the UI, I thought we could make an improvement here by giving a little more info as to why the UI cannot make a unique ID. This is currently semi-hidden away in the javascript console, but we could potentially surface this in the UI itself as a larger task. I figured this smaller task could help folks in the meantime if they hit upon this as they might open up the javascript console themselves to see whats up and they'd at least get this extra clue. |
||
---|---|---|
.. | ||
dom | ||
editor | ||
filter | ||
form | ||
helpers | ||
http | ||
intl | ||
routing | ||
search | ||
storage | ||
ticker | ||
ascend.js | ||
atob.js | ||
btoa.js | ||
callable-type.js | ||
create-fingerprinter.js | ||
distance.js | ||
get-environment.js | ||
get-form-name-property.js | ||
isFolder.js | ||
keyToArray.js | ||
left-trim.js | ||
maybe-call.js | ||
merge-checks.js | ||
minimizeModel.js | ||
non-empty-set.js | ||
promisedTimeout.js | ||
right-trim.js | ||
templatize.js | ||
tomography.js | ||
ucfirst.js | ||
update-array-object.js |