Abstract type UX improvements
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Is your feature request related to a problem? Please describe.
When working with abstract types in the editor it should always be clear which implementation type is being used. Both in properties and lists/dictionaries.
See discussion in #1842
Also if selected type is not an EntityComponent we should hide the component picker.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in #1842 and inspect the editor behavior for abstract types in properties, lists, and dictionaries. Check how the component picker behaves when the selected type is not an EntityComponent. Done means the implementation type is always clear and the picker is hidden for non-EntityComponent types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100