Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a5
Issue ID
1059789
Regression
No
Package Manager - Naming convention inconsistencies
Package Manager - Naming convention inconsistencies
There are some naming inconsistencies in the Package Manager UI. As the UI contains more and more packages it's important that it's easy to read and consistaint.
As of 2018.1 some package names have spaces, some camelCase and some dashes. I know this will come accross as pedantic but the UI is starting to look a little messy.
Some Examples of Package names below.
- In App Purchasing (Spaces)
- IncrementalComplier (Camel Case)
- TextMesh Pro (Camel Case and Spaces)
- Render-Pipeline.Core (Dashes and dots)
- Oculus (Andriod)
- Oculus (Standalone)
We don't need the brackets. Oculus Standalone, then Oculus Andriod, Oculus Xbox1060 etc would be better.
- Render-Pipelines.high-Definition ("high" not capital dashes and dots)
- Entities - Should be "Entity Component System" or "ECS" as it's more commonly known in the community.
- Vectorgraphics - should be Vector Graphics
It would be great to have some guidelines to help Dev and QA keep packman tidy and presentable.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment