Search Issue Tracker
By Design
Votes
0
Found in
5.0.0b20
Issue ID
664744
Regression
No
Having a member with the same name as one of the removed component accessors causes warnings
Since rigidbody and other direct component accessors have been deprecated to GetComponent<Component>() Unity shouldn't warn that previously valid component accessor hides the inherited member as there should be no member to hide.
Steps to reproduce:
1. Download attached project
2. See the warning:
Assets/MyPhysicsScript.cs(7,19): warning CS0108: `MyPhysicsScript.rigidbody' hides inherited member `UnityEngine.Component.rigidbody'. Use the new keyword if hiding was intended
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Usability] Process details under Threads in Profiler can't be scrolled when the info doesn't fit the pop-up vertically
- Target selection menu in Profiler has no highlight when hovering on various options
- [Usability] Can't create Target Frame Time presets in Profiler
- Text is not displayed in the Inspector window when using Korean characters
- [macOS][iOS][IL2CPP] Crash when using the nullable enum as a parameter and passing a default value into it.
Soraphis
Jun 14, 2018 10:42
We're now in 2018 and this is still a thing.
i know the warning is by design, but why are the properties in the base class not removed?
BrainAndBrain
Sep 10, 2016 18:10
How, or rather why, is this by design? We're well past the release that deprecated component accessors, and this warning only serves to confuse.