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
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.