Level 1 portals show incorrect "resonator level(s) needed for next portal level"

[Artoria2e5]

I have a portal that's level 1 from a single level 5 resonator. It should require 11 more resonator levels to become level 2. However, IITC says 8, probably because it doesn't quite understand how level 1 works differently from all other levels:

[Artoria2e5]

Specifically,

ingress-intel-total-conversion/core/code/portal_info.js

Line 14 in 199c9f7

window.getPortalLevel = function(d) {

applies a minimum clamp to the level, so that it does not return a number less than 1 when there's a resonator. However,

ingress-intel-total-conversion/core/code/portal_detail_display.js

Line 121 in 199c9f7

levelDetails = getPortalLevel(details);

naively treats the detailed level as total level / 8.

[Artoria2e5]

Considering that the only references to getPortalLevel in this whole organization are:

• a deprecated.js
• this portal_detail_display.js
• portal_info.js, getPortalRange()

I'd think we can get away with removing the Math.max() in getPortalLevel. The only place where the max makes sense is in getPortalRange() -- we can just put it there!

[McBen]

and

ingress-intel-total-conversion/core/code/portal_info.js

Lines 366 to 370 in 199c9f7

	window.getPortalSummaryData = function(d) {
	// NOTE: the summary data reports unclaimed portals as level 1 - not zero as elsewhere in IITC
	var level = parseInt(getPortalLevel(d));
	if (level == 0) level = 1; //niantic returns neutral portals as level 1, not 0 as used throughout IITC elsewhere

it would handle the "without max" case, but makes the comments invalid