Closes

Describe your changes:

Closes #7947

This change adds a new case to the existing 3 logic scenarios in the ClearData function (new case in bold):

• if no domain object (clear data)
• else if the object requesting the clear is the same as the currently plotting object (clear data)
• else if the object requesting the clear's composition contains the currently plotting object (clear data)
• else if the object requesting the clear is within the composition of the currently plotting object (clear data)

I maintain that the 3rd case, compositionPathContainsId may have originally been intended to capture the 4th case, but I don't want to break someone else's work so it is safer to just cover the currently missing 4th case.

To test this change, you'll have to do the following:

1. Add 'openmct.objectViews.emit('clearData',domainObject);'
   to the TelemetryMeanProvider.
2. Create a new mean object and select it in the tree.
3. Put the mean object into an overlay plot and zoom out. The mean should be re-calculated and re-plotted on every zoom level.

Note: This is much easier to test with a server responding to telemetry requests as opposed to using sine wave generators.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Is this a notable change that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?

Author Checklist

• Changes address original issue?
• Tests included and/or updated with changes?
• Has this been smoke tested?
• Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.
• Have you associated a milestone with this PR? Note: leave blank if unsure.
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Reviewer has tested changes by following the provided instructions?
• Changes appear not to be breaking changes?
• Appropriate automated tests included?
• Code style and in-line documentation are appropriate?