Search Issue Tracker
Fixed
Fixed in 6000.1.1f1, 6000.2.0a9
Votes
1
Found in
2022.3.0f1
6000.0.0b1
6000.1.0a1
6000.2.0a1
7000.0.0a1
Issue ID
UUM-101208
Regression
No
Search CustomIndexer workflow using IndexProperty doesn't work if property name is not lowercase
More context on this bug: [https://unity.slack.com/archives/CGL2NFY0N/p1742826397189369]
Object.Indexer.IndexProperty doesn't lowercase the property name. Which means if a user registers a property not fully lower case, the user won't be able to find it.
* IndexProperty<PropertyType, PropertyOwnerType> : should have a version with saveKeyword and exact at false
* We should have a manual section to explain how to do CustomIndexing
* This blog post should be updated on all these gotchas: [https://github.com/Unity-Technologies/com.unity.search.extensions/wiki/Custom-Asset-Indexing]
* We should have a template script to create a CustomIndexer with a valid example.
Comments (1)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
sabiomarkanthony44
Mar 25, 2025 15:32
Search CustomIndexer workflow using IndexProrpety doesn't work if property name is not in lowercase