Boolean

link GraphQL Schema definition

link Require by

• ActionStatusFilterA filter to be used against ActionStatus fields. All fields are combined with a logical ‘and.’
• ActionTypeFilterA filter to be used against ActionType fields. All fields are combined with a logical ‘and.’
• BigFloatFilterA filter to be used against BigFloat fields. All fields are combined with a logical ‘and.’
• BooleanFilterA filter to be used against Boolean fields. All fields are combined with a logical ‘and.’
• CameraStatusFilterA filter to be used against CameraStatus fields. All fields are combined with a logical ‘and.’
• CameraTypeFilterA filter to be used against CameraType fields. All fields are combined with a logical ‘and.’
• DatetimeFilterA filter to be used against Datetime fields. All fields are combined with a logical ‘and.’
• DeploymentStatusFilterA filter to be used against DeploymentStatus fields. All fields are combined with a logical ‘and.’
• DetectionItemTypeFilterA filter to be used against DetectionItemType fields. All fields are combined with a logical ‘and.’
• DeviceModesFilterA filter to be used against DeviceModes fields. All fields are combined with a logical ‘and.’
• GeometryTypeFilterA filter to be used against GeometryType fields. All fields are combined with a logical ‘and.’
• Imagenull
• ImageAnnotationnull
• ImageAnnotationConditionA condition to be used against `ImageAnnotation` object types. All fields are tested for equality and combined with a logical ‘and.’
• ImageAnnotationInputAn input for mutations affecting `ImageAnnotation`
• ImageAnnotationPatchRepresents an update to a `ImageAnnotation`. Fields that are set will be updated.
• ImageConditionA condition to be used against `Image` object types. All fields are tested for equality and combined with a logical ‘and.’
• ImageInputAn input for mutations affecting `Image`
• ImagePatchRepresents an update to a `Image`. Fields that are set will be updated.
• ImageTypeFilterA filter to be used against ImageType fields. All fields are combined with a logical ‘and.’
• JSONFilterA filter to be used against JSON fields. All fields are combined with a logical ‘and.’
• Modelnull
• ModelConditionA condition to be used against `Model` object types. All fields are tested for equality and combined with a logical ‘and.’
• ModelDeploymentRulenull
• ModelDeploymentRuleConditionA condition to be used against `ModelDeploymentRule` object types. All fields are tested for equality and combined with a logical ‘and.’
• ModelDeploymentRuleInputAn input for mutations affecting `ModelDeploymentRule`
• ModelDeploymentRulePatchRepresents an update to a `ModelDeploymentRule`. Fields that are set will be updated.
• ModelInputAn input for mutations affecting `Model`
• ModelPatchRepresents an update to a `Model`. Fields that are set will be updated.
• ModelStatusFilterA filter to be used against ModelStatus fields. All fields are combined with a logical ‘and.’
• ModelTypeFilterA filter to be used against ModelType fields. All fields are combined with a logical ‘and.’
• Organizationnull
• OrganizationConditionA condition to be used against `Organization` object types. All fields are tested for equality and combined with a logical ‘and.’
• OrganizationInputAn input for mutations affecting `Organization`
• OrganizationPatchRepresents an update to a `Organization`. Fields that are set will be updated.
• OrgUsernull
• OrgUserConditionA condition to be used against `OrgUser` object types. All fields are tested for equality and combined with a logical ‘and.’
• OrgUserPatchRepresents an update to a `OrgUser`. Fields that are set will be updated.
• PageInfoInformation about pagination in a connection.
• Servernull
• ServerConditionA condition to be used against `Server` object types. All fields are tested for equality and combined with a logical ‘and.’
• ServerPatchRepresents an update to a `Server`. Fields that are set will be updated.
• StringFilterA filter to be used against String fields. All fields are combined with a logical ‘and.’
• StringListFilterA filter to be used against String List fields. All fields are combined with a logical ‘and.’
• UUIDFilterA filter to be used against UUID fields. All fields are combined with a logical ‘and.’
• UUIDListFilterA filter to be used against UUID List fields. All fields are combined with a logical ‘and.’
• __DirectiveA Directive provides a way to describe alternate runtime execution and type validation behavior in a GraphQL document. In some cases, you need to provide options to alter GraphQL's execution behavior in ways field arguments will not suffice, such as conditionally including or skipping a field. Directives provide this by describing additional information to the executor.
• __EnumValueOne possible value for a given Enum. Enum values are unique values, not a placeholder for a string or numeric value. However an Enum value is returned in a JSON response as a string.
• __FieldObject and Interface types are described by a list of Fields, each of which has a name, potentially a list of arguments, and a return type.
• __InputValueArguments provided to Fields or Directives and the input fields of an InputObject are represented as Input Values which describe their type and optionally a default value.
• __TypeThe fundamental unit of any GraphQL Schema is the type. There are many kinds of types in GraphQL as represented by the `__TypeKind` enum. Depending on the kind of a type, certain fields describe information about that type. Scalar types provide no information beyond a name, description and optional `specifiedByUrl`, while Enum types provide their values. Object and Interface types provide the fields they describe. Abstract types, Union and Interface, provide the Object types possible at runtime. List and NonNull types compose other types.