Handles LookupKey.Boolean

Hierarchy (view full)

Constructors

Properties

badTextMessage: "Invalid value" = 'Invalid value'

Accessors

  • get supportedCultures(): string[]
  • All cultureIds that support the order and separator. Note that if there is language-specific culture and one that is not language specific but has the same local, you can define just the one for the local because the DataTypeParser service will search both language specific and language agnostic when the CultureService is setup with fallbacks.

    Returns string[]

Methods

  • If the user needs to abandon this instance, they should use this to clean up active resources (like timers) and to release memory that would stall the garbage collector from disposing this object. It should assign any object reference to undefined as a strong indicator that the object has been disposed.

    Returns void

  • Changes the text if needed before parsing. Usually removes unwanted characters like trimming whitespace, but it could try to fix the data to closely resemble the desired text pattern that will be parsed by parseCleanedText. When it comes to strings as the native data type, it can rework the text to be the pattern expected for storage. For example, you might store a US phone number in this pattern: [3 digits]-[3 digits]-[4 digits]. The user may enter it in another familiar pattern like "(413) 555-0521" or "413 555 0520". This would clean it up to the desired pattern of "413-555-0521".

    Parameters

    • text: string
    • dataTypeLookupKey: string
    • cultureId: string

    Returns string

  • Since there can be several parsers for a single lookupKey and cultureID that are selected based on the text, this function is used when you want all possible candidates. It is effectively supports() without the text.

    Parameters

    • dataTypeLookupKey: string
    • cultureId: string

    Returns boolean

Generated using TypeDoc v0.25.12