Skip to content
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.

Encapsulating condition sets by types #978

Closed
derpdead opened this issue Jul 16, 2021 · 0 comments
Closed

Encapsulating condition sets by types #978

derpdead opened this issue Jul 16, 2021 · 0 comments
Assignees
Labels
Core Functionality feature (type) New feature

Comments

@derpdead
Copy link
Contributor

Motivation

Currently every condition type is generated by:

        typeComponent() {
            switch (this.parameter.type) {
            case TYPES.SELECT:
            case TYPES.MULTI_SELECT:
                return () => import('@UI/components/Select/TranslationSelect');
            case TYPES.TEXT:
            case TYPES.UNIT:
            case TYPES.NUMERIC:
                return () => import('@UI/components/TextField/TextField');
            default:
                return null;
            }
        },

which is limited to UI comonents.

Implementation

Each condition type should generate dynamically component with pattern

() => import(`@Conditions/components/TreeDesigner/Item/ConditionTreeDesigner${conditionType}Item`)
@derpdead derpdead added Core Functionality feature (type) New feature labels Jul 16, 2021
@derpdead derpdead self-assigned this Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Core Functionality feature (type) New feature
Projects
None yet
Development

No branches or pull requests

1 participant