Data node config attributes: filter and sort

[FlorianJacta]

Description There are two objectives:

• the first one to have a unique and fixed order for properties in Taipy Studio details section;
  • The first idea was to group properties based on their nature: Common and required | Common and optional | Specific and required | Specific and optional
  • Then, in these different groups, have an order that makes sense. (Example for SQL: Host, Username, Password, ...)
• the second objective is to know the optional and required properties for Data Nodes.
  • Changing the storage type of a Data Node should write the mandatory properties for this storage in the Details section.
  • When adding a new property, displayed properties should only be relevant to this storage type.

[FredLL-Avaiga]

to declare order, specify taipy_index (int) attribute in schema file ex:

"scope": {
            "description": "An enum value among GLOBAL, CYCLE, SCENARIO or PIPELINE that represents the visibility of the data node in the graph of entities.",
            "type": "string",
            ...
            "taipy_index": 1
          },

[FredLL-Avaiga]

I suppose that the required properties information is already present in the schema through the if/then/else and required directives

[jrobinAV]

to declare order, specify taipy_index (int) attribute in schema file ex:

Taipy can be responsible for the business logic but not how it is displayed in a graphical interface. I propose Studio to be responsible for the order.

Taipy can provide the list of shared mandatory params, mandatory params specific for each storage type, and optional params specific for each storage type. The order should be decided by Taipy-studio-config.

I would personally use the following order:

• The shared mandatory params in alphabetical order
• The mandatory params specific to a storage type in alphabetical order
• The optional params specific to a storage type in alphabetical order

[jrobinAV]