why bother going through the artifact layers to get the target data - it's already in the portal details!!
This commit is contained in:
@ -190,11 +190,10 @@ window.getPortalMiscDetails = function(guid,d) {
|
||||
// artifacts - tacked on after (but not as part of) the 'randdetails' table
|
||||
// instead of using the existing columns....
|
||||
|
||||
// fill in target status from the artifact code
|
||||
var targets = artifact.getPortalTarget(guid);
|
||||
if (targets) {
|
||||
if (d.artifactBrief && d.artifactBrief.target && Object.keys(d.artifactBrief.target).length > 0) {
|
||||
var targets = Object.keys(d.artifactBrief.target);
|
||||
//currently (2015-07-10) we no longer know the team each target portal is for - so we'll just show the artifact type(s)
|
||||
randDetails += '<div id="artifact_target">Target portal: '+Object.keys(targets).map(function(x) { return x.substr(0,1).toUpperCase()+x.substr(1); }).join(', ')+'</div>';
|
||||
randDetails += '<div id="artifact_target">Target portal: '+targets.map(function(x) { return x.capitalize(); }).join(', ')+'</div>';
|
||||
}
|
||||
|
||||
// shards - taken directly from the portal details
|
||||
|
Reference in New Issue
Block a user