Hoogle Search
Within LTS Haskell 24.65 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
-
gogol-sheets Gogol.Sheets.Types Selects DeveloperMetadata that matches all of the specified fields. For example, if only a metadata ID is specified this considers the DeveloperMetadata with that particular unique ID. If a metadata key is specified, this considers all developer metadata with that key. If a key, visibility, and location type are all specified, this considers all developer metadata with that key and visibility that are associated with a location of that type. In general, this selects all DeveloperMetadata that matches the intersection of all the specified fields; any field or combination of fields may be specified. See: newDeveloperMetadataLookup smart constructor.
-
gogol-sheets Gogol.Sheets.Types No documentation available.
newtype
DeveloperMetadataLookup_LocationMatchingStrategy gogol-sheets Gogol.Sheets.Types Determines how this lookup matches the location. If this field is specified as EXACT, only developer metadata associated on the exact location specified is matched. If this field is specified to INTERSECTING, developer metadata associated on intersecting locations is also matched. If left unspecified, this field assumes a default value of INTERSECTING. If this field is specified, a metadataLocation must also be specified.
-
gogol-sheets Gogol.Sheets.Types No documentation available.
-
gogol-sheets Gogol.Sheets.Types Default value. This value must not be used.
-
gogol-sheets Gogol.Sheets.Types Indicates that a specified location should be matched exactly. For example, if row three were specified as a location this matching strategy would only match developer metadata also associated on row three. Metadata associated on other locations would not be considered.
-
gogol-sheets Gogol.Sheets.Types Indicates that a specified location should match that exact location as well as any intersecting locations. For example, if row three were specified as a location this matching strategy would match developer metadata associated on row three as well as metadata associated on locations that intersect row three. If, for instance, there was developer metadata associated on column B, this matching strategy would also match that location because column B intersects row three.
newtype
DeveloperMetadataLookup_LocationType gogol-sheets Gogol.Sheets.Types Limits the selected developer metadata to those entries which are associated with locations of the specified type. For example, when this field is specified as ROW this lookup only considers developer metadata associated on rows. If the field is left unspecified, all location types are considered. This field cannot be specified as SPREADSHEET when the locationMatchingStrategy is specified as INTERSECTING or when the metadataLocation is specified as a non-spreadsheet location: spreadsheet metadata cannot intersect any other developer metadata location. This field also must be left unspecified when the locationMatchingStrategy is specified as EXACT.
DeveloperMetadataLookup_LocationType :: Text -> DeveloperMetadataLookup_LocationTypegogol-sheets Gogol.Sheets.Types No documentation available.
pattern
DeveloperMetadataLookup_LocationType_Column :: DeveloperMetadataLookup_LocationTypegogol-sheets Gogol.Sheets.Types Developer metadata associated on an entire column dimension.