Unset Gauge limits are being handled as 0

[charlesh88]

Summary

If a low and/or high limit is not set for a Gauge, it is treated by the Gauge as if it was actually set to 0. Instead, that limit should not be displayed at all. The fix here is to use a v-if="lowLimit !== empty instead of the current null check.

Steps to Reproduce

1. Edit props:

2. Observe: limits are displayed properly.

3. Edit properties to remove limit definitions

4. Observe: limits should not be displayed, but are.

Environment

• Open MCT Version:
• Deployment Type:
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?

Testing Notes

1. Create a Gauge view or edit existing.
2. Repeat steps 1 - 4 in 'Steps to Reproduce' above.
3. Verify that limits are not displayed, and the Gauge looks similar to this:
   

[charlesh88]

A fix for this caused a regression that made the limits not display at all. Work being done in the gauge-fixes branch by @charlesh88 will fix this.

[michaelrogers]

During testathon 06/15/2022, a regression on gauge low/high limits was observed. If a user sets a range low and a range high value, it is not displayed in any of the gauge types


.

[ozyx]

Testathon 6/23/22:

Verified that after removing limits, the min and max values are displayed instead.

Still need to verify this, misunderstood directions 😔

Caveat:

• Ran into issues with properties persisting after changing them. Had to focus a different object and come back to the Gauge in order for the property changes to persist. Seems likely a separate issue?

[alizenguyen]

Testathon 6/27/22:

Still see what Jesse is seeing about the property change is not implemented until you move to a different object and come back.

[ozyx]

Testathon 6/27/22:

Could not get Gauge limits to show up at all-- Gauge stayed completely grey with various limit values

[unlikelyzero]

General issue filed here #5398 Will reverify

[charlesh88]

Testing Notes

See #5323

[davetsay]

verified (although i had to create two gauges to compare as there is a forms mutation bug preventing exact replication steps from working)