Only attempt to clear measures if we created the measure

[chrisui]

This fixes an issue where if we decided not to create a measurement we would clear ALL measurements from the performance entry buffer due to passing undefined as the entry name.

The original bug here means any performance entries the user might have in their application will be inadvertently nuked.

For reference see the performance.clearMeasures spec.

Todo

• Test/s incoming (would love some help in finding where to add such a test!)

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

If you are contributing on behalf of someone else (eg your employer): the individual CLA is not sufficient - use https://developers.facebook.com/opensource/cla?type=company instead. Contact cla@fb.com if you have any questions.

[chrisui]

Would love some assistance in targeting where to add a test for this. Can't seem to find any existing tests to add a new case to.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[gaearon]

This seems fine as is, thanks! We don’t need a test because this code will be deleted in the next release (the perf integration is in a different place in Fiber). I think the new code doesn’t have this issue, but you can check ReactDebugFiberPerf to make sure.

I’ll make a note to cherry-pick this commit in 15.6.

[chrisui]

@gaearon Thanks for the quick turnaround Dan!