Hoogle Search

Within LTS Haskell 24.62 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. reverseLookupConfig :: ManagedZone -> Maybe ManagedZoneReverseLookupConfig

    gogol-dns Gogol.DNS.Types

    The presence of this field indicates that this is a managed reverse lookup zone and Cloud DNS resolves reverse lookup queries using automatically configured records for VPC resources. This only applies to networks listed under privatevisibilityconfig.

  2. cacheLookup :: HttpRequest -> Maybe Bool

    gogol-logging Gogol.Logging

    Whether or not a cache lookup was attempted.

  3. cacheLookup :: HttpRequest -> Maybe Bool

    gogol-logging Gogol.Logging.Types

    Whether or not a cache lookup was attempted.

  4. data DeveloperMetadataLookup

    gogol-sheets Gogol.Sheets

    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.

  5. DeveloperMetadataLookup :: Maybe DeveloperMetadataLookup_LocationMatchingStrategy -> Maybe DeveloperMetadataLookup_LocationType -> Maybe Int32 -> Maybe Text -> Maybe DeveloperMetadataLocation -> Maybe Text -> Maybe DeveloperMetadataLookup_Visibility -> DeveloperMetadataLookup

    gogol-sheets Gogol.Sheets

    No documentation available.

  6. newtype DeveloperMetadataLookup_LocationMatchingStrategy

    gogol-sheets Gogol.Sheets

    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.

  7. DeveloperMetadataLookup_LocationMatchingStrategy :: Text -> DeveloperMetadataLookup_LocationMatchingStrategy

    gogol-sheets Gogol.Sheets

    No documentation available.

  8. pattern DeveloperMetadataLookup_LocationMatchingStrategy_DEVELOPERMETADATALOCATIONMATCHINGSTRATEGYUNSPECIFIED :: DeveloperMetadataLookup_LocationMatchingStrategy

    gogol-sheets Gogol.Sheets

    Default value. This value must not be used.

  9. pattern DeveloperMetadataLookup_LocationMatchingStrategy_EXACTLOCATION :: DeveloperMetadataLookup_LocationMatchingStrategy

    gogol-sheets Gogol.Sheets

    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.

  10. pattern DeveloperMetadataLookup_LocationMatchingStrategy_INTERSECTINGLOCATION :: DeveloperMetadataLookup_LocationMatchingStrategy

    gogol-sheets Gogol.Sheets

    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.

Page 245 of many | Previous | Next