BH.oM.Data.Requests.LogicalNotRequest¶

IRequest that inverts the query specified by the input request, i.e. any object that fits this request will be excluded from a pull.

Class structure¶

Implemented interfaces and base types¶

The LogicalNotRequest is inheriting from the following base type(s) and implements the following interfaces:

BH.oM.Data.Requests.ILogicalRequest
BH.oM.Data.Requests.IRequest
BH.oM.Base.IObject

Properties¶

Defining properties¶

The following properties are defined on the class

Name	Type	Description	Quantity
Request	IRequest	Request to be inverted, i.e. defining what should be excluded.	-

Derived properties¶

The following properties are defined as extension methods in one of the BHoM_Engines

Name	Type	Description	Quantity	Engine
Discipline	Nullable<Discipline>	Gets discipline enforced by the Request. If the result is different than defaultDiscipline and neither of two is Undefined, null is returned (the result discipline is conflicting with defaultDiscipline).	-	Revit_Engine
IFilterDescription	string	Returns a description of the filter represented by the given IRequest.	-	Revit_Engine
IRequests	List<IRequest>	-	-	Data_Engine
Requests	List<IRequest>	-	-	Data_Engine

Code and Schema¶

C# implementation¶

C#

public class LogicalNotRequest : BH.oM.Data.Requests.ILogicalRequest, BH.oM.Data.Requests.IRequest, BH.oM.Base.IObject

Assembly: Data_oM.dll

The C# class definition is available on github:

LogicalNotRequest.cs

All history and changes of the class can be found by inspection the history.

JSON Schema implementation¶

The object is defined as a JSON schema. You can validate a JSON instance against this schema by reference. To do this, use the schema reference below in a validator like this one.

JSON Schema

{
 "$ref" : "https://raw.githubusercontent.com/BHoM/BHoM_JSONSchema/develop/Data_oM/Requests/LogicalNotRequest.json"
}

The JSON Schema is available on github here:

LogicalNotRequest.json