Boolean

link GraphQL Schema definition

link Require by

• AccountingCompanynull
• AccountingCompanyConditionA condition to be used against `AccountingCompany` object types. All fields are tested for equality and combined with a logical ‘and.’
• ClientCompanynull
• ClientCompanyConditionA condition to be used against `ClientCompany` object types. All fields are tested for equality and combined with a logical ‘and.’
• Invoicenull
• InvoiceConditionA condition to be used against `Invoice` object types. All fields are tested for equality and combined with a logical ‘and.’
• PageInfoInformation about pagination in a connection.
• __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.
• __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 and description, 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.