feature request #10337
closedAllow supportedCategoricalEnumeration and recommendedModfiers for term collection
70%
Description
... not only for vocabularies
These lists should be adapted as good as possible to the needs of a given project, so it should be much more flexibel then when using vocabularies only.
Related issues
Updated by Andreas Müller over 1 year ago
- Related to bug #10340: Categorical and Quantitative Data details view must only show recommended modifiers added
Updated by Andreas Müller over 1 year ago
- Status changed from New to Resolved
- Assignee changed from Andreas Müller to Katja Luther
- Priority changed from New to Highest
- % Done changed from 0 to 70
This should be fixed. Please review (especially if all functionality still works and if the code looks correct). I also did some renaming of classes in taxEditor to have it more consistent.
Can you also check if all classes are still needed?
There are e.g. classes like
RecommendedModifierCollectionsCollectionSection/RecommendedModifierCollectionsDtoCollectionSection
RecommendedModifierCollectionsElement/RecommendedModifierDtoCollectionsElement
RecommendedStateCollectionElement/RecommendedStateCollectionsDtoElement
RecommendedStateCollectionSection/RecommendedStateDtoCollectionsSection
Can the non-dto classes be deleted?
Updated by Andreas Müller over 1 year ago
Please also check if #10340 can easily be fixed as it is related to this ticket.
Updated by Katja Luther over 1 year ago
- Status changed from Resolved to Closed
- Assignee changed from Katja Luther to Andreas Müller
Andreas Müller wrote in #note-2:
This should be fixed. Please review (especially if all functionality still works and if the code looks correct). I also did some renaming of classes in taxEditor to have it more consistent.
Can you also check if all classes are still needed?
There are e.g. classes like
RecommendedModifierCollectionsCollectionSection/RecommendedModifierCollectionsDtoCollectionSection
RecommendedModifierCollectionsElement/RecommendedModifierDtoCollectionsElement
RecommendedStateCollectionElement/RecommendedStateCollectionsDtoElement
RecommendedStateCollectionSection/RecommendedStateDtoCollectionsSectionCan the non-dto classes be deleted?
I tested to add a tree as recommended state collection and as recommended modifier collection, this worked as expected.
Currently we need the dto and the non-dto elements because the vocabulary view still uses cdm entities
Updated by Andreas Müller about 1 year ago
- Related to bug #10377: Changing recommended state collection in Character editor throws NPE added