Consider downgrading "Repeated property access of built in component is inefficient" to hint

Accessing a property of a built in component can be inefficient because it's transitioning to native code multiple times for unchanged data. Currently, this is a warning, but it might be more appropriate to mark as a hint, especially in non-critical code paths

No file or test is identified in the issue. Start by searching for the inspection named “Repeated property access of built in component is inefficient”; done means its severity is downgraded from warning to hint, with any relevant existing verification updated.

Written by the indexing model from the issue text.