Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.3.0b9
Issue ID
1388926
Regression
No
ListView events do not follow Unity's coding conventions
Unity's coding convention requires event to:
"Include one participle-form verb in the event name (generally ending in -ed or -ing, ex. occurred, loading, started, given)"
https://ono.unity3d.com/unity-extra/unity-meta/raw/@/ReferenceSource/CSharp/Assets/CSharpReference.cs
See the events here:
https://docs.unity3d.com/Packages/com.unity.ui@1.0/api/UnityEngine.UIElements.ListView.html#events
We should obsolete the current event members and introduce new ones (we should also make sure to keep old ones functional).
Slack convo that brought this up: https://unity.slack.com/archives/C3414V4UV/p1639479677020200
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
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
Resolution Note (fix version 2022.2):
Fixed 1388926: ListView events do not follow Unity's coding conventions