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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.