Attribute Type Validation at the Front End

[aahei]

New feature: Attribute Type Validation in Workflow Editor

Problem: Most operators only take input attributes of particular types for their fields. For example, the sentiment analysis operator only accepts string-typed attributes as input. However, there isn't any type-checking mechanism at the front end to check the type of attributes users selected, and they can't find the error until they run the workflow.

Solution: Implement the attribute type validation at the front end using the type constraint information from the schema from the back end. That is, accepted attribute type information is transmitted within the operators' schemas and enforced at the front end, which requires changing the operator schema structure. It involves using formly at the front end and modifying the Jackson JSON Schema Generator library at the back end.

[aahei]

There will be a third PR adding the attribute type rules for the rest operators when they have been fixed in #1954 , #1955 .

[shengquan-ni]

No critical need for this, close it.