Currently any search involving a logical expression consisting of field, operator, and value provides the value in the form of a composite argument:
value: {
value: "The actual value",
type: "The type of the value, the above string is going to be translated to.
}
We want to refactor this to be more intuitive.
value and valueType where valueType is a GraphQL Enum that enables selection of the appropriate type, where value is required, and valueType is not required.
Enum of types
Use the basic GraphQL types and additionally our introduced custom ISO-Date, ISO-Time, and ISO-DateTime types.
Affected modules / projects
This issue affects both the GraphQL server as well as the single-page-application, involving each the "skeleton" and the "code-generator" sub-projects.
Currently any search involving a logical expression consisting of
field,operator, andvalueprovides thevaluein the form of a composite argument:We want to refactor this to be more intuitive.
valueandvalueTypewhere valueType is a GraphQL Enum that enables selection of the appropriate type, wherevalueis required, andvalueTypeis not required.Enum of types
Use the basic GraphQL types and additionally our introduced custom ISO-Date, ISO-Time, and ISO-DateTime types.
Affected modules / projects
This issue affects both the GraphQL server as well as the single-page-application, involving each the "skeleton" and the "code-generator" sub-projects.