Search Issue Tracker
Fixed
Fixed in 2022.3.21f1, 2023.2.13f1, 6000.0.0b11
Votes
0
Found in
2023.2.0a1
2023.3.0a1
6000.0.0b11
Issue ID
UUM-61220
Regression
No
[Advanced Project Search] typing t:script yields unwanted result
* Ensure project browser is using Advanced Search (Preferences -> Search -> Project Advanced)
* type t:script
* see that a lot of unwanted results are displayed. It is because t:script act as a contain and matches t:ScriptablerObject. !image-2024-01-22-10-19-18-694.png!
* We have code in place to convert type queries to *t=* but it doesn't seem to be invoked BEFORe the search query is sent to the backend.
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
- "EndLayoutGroup: BeginLayoutGroup must be called first" error is thrown when changing Shader Precision Model from the Build Profiles window
- White artifacts/outlines are visible in the Garden Scene when viewing at meshes from a distance
- Shader warnings "Sprite-Unlit-Default" are thrown after building 2D Platrformer Microgame Template
- [Android] HLSL shader becomes corrupted when running on an Android device
- Missing spaces in "Welcome to VR Mutiplayer Template Project" Welcome Dialog window
Resolution Note (fix version 2023.2.13f1):
Editor: Project Browser in AdvanceSearchEngine treats all t: and l: as t= and l=
Resolution Note (fix version 2022.3.21f1):
Editor: Project Browser in AdvanceSearchEngine treats all t: and l: as t= and l=