Metadata
- Source
- FLUID-5784
- Type
- Improvement
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- Antranig Basman
- Reporter
- Antranig Basman
- Created
2015-10-04T11:09:05.120-0400 - Updated
2021-08-08T13:57:15.662-0400 - Versions
-
- 2.0
- 3.0
- Fixed Versions
-
- 6.0
- Component
-
- IoC System
Description
For historical reasons (mainly, since in the 1.x-era framework, detection of components in the tree was extremely primitive and duck-type-based), the top-level property encoding a component's "type" (derived from the "type" field of a subcomponent or constructor name) came to be called "typeName". This causes unnecessary confusion to users as well as using up a new top-level name in a collision-prone way.
We should at the same time take the opportunity to regularise the name "gradeNames" into something more directly descriptive such as "parentGrades" or even "parents". This should be done at the same time as the "options flattening revolution" FLUID-5750 since that will already be a disruptive enough change.