| Summary: | Support dynamic list of child element types | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ling Hao <ling.hao> |
| Component: | Sapphire | Assignee: | Konstantin Komissarchik <konstantin> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | konstantin |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ling Hao
I think that rather than implementing type enablement, we should look at supporting a dynamic list of possible child element types for element and list properties. This would solve this requirement as you would be able to vary the set of possible types based on a criteria and would also enable extensibility where third parties wish to contribute new types to an existing model. This has been implemented for a while now. Somehow the bug hasn't been resolved. See PossibleTypesService in the docs. Please verify. Verify via sapphire-gallery's custom PossibleTypeService. |