Search Issue Tracker
Fixed
Fixed in 2022.3.30f1, 6000.0.0f1
Votes
0
Found in
2022.3.0f1
2023.2.0a1
2023.3.0a1
6000.0.37f1
Issue ID
UUM-61280
Regression
No
[Properties] Property Search doesn't work with properties with the same path
Both during asset indexing or scene search we index properties by property path. But if 2 types/components have components with the same name (width, enabled) these properties overrides themselves. There is no Type differentiator.
Also, when doing when searching we return the first match of a given property path which might not be what the user is looking for.
Potential fixes should be done in multiple parts:
- Search Proposition dialog, should only show properties relative to all types that are part of the results of the query.
* Due to the fact that we do not want to load assets, and that we do not have access to types of the component in prefab we cannot realiably implement this feature.
When indexing Enum shouldn't use IndexPropertyStringComponent. No variation of indexing are needed.
- We need to update the Find Similar Property workflow with the component type.
- Can we try to cache the Propositions of Scene and Asset providers.
- SearchProposition should contains the Complete property path, including the component type: MeshRenderer.m_Enabled
- When indexing, we index both complete property path and short property path (wihout type)
- When searching the scene, OnPropertyFilter should check if the property name contains a type and only search in that component.
- Property values stored in the PropertyDatabase should be store with the full path, since multiple properties might have the same name and override each other).
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.0.0f1):
Search: Support component name prefix when searching component properties.
Resolution Note (fix version 2022.3.30f1):
Search: Support component name prefix when searching component properties.