Hoogle Search

Within LTS Haskell 24.66 (ghc-9.10.3)

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

  1. TFormatAsTemporal :: TextChannel

    hvega Graphics.Vega.VegaLite

    The text marks should be formatted as dates or times. Use a d3 date/time format string with TFormat.

  2. TimeFormat :: Text -> ConfigurationProperty

    hvega Graphics.Vega.VegaLite

    Deprecated: Please change TimeFormat to TimeFormatStyle

  3. TimeFormatStyle :: Text -> ConfigurationProperty

    hvega Graphics.Vega.VegaLite

    The default time format for raw time values (without time units) in text marks, legend labels, and header labels. This does not control the appearance of axis labels. The default is "%b %d, %Y". This was renamed from TimeFormat in 0.6.0.0.

  4. data TransformSpec

    hvega Graphics.Vega.VegaLite

    Represent a transformation (input to transform). It is expected that routines like calculateAs and filter are used to create values with this type, but they can also be constructed and deconstructed manually with toTransformSpec and fromTransformSpec.

  5. VLTransform :: VLProperty

    hvega Graphics.Vega.VegaLite

    See transform.

  6. fromTransformSpec :: TransformSpec -> VLSpec

    hvega Graphics.Vega.VegaLite

    Extract the contents of a transformation specification. This may be needed when the Vega-Lite specification adds or modifies settings for a particular encoding, and hvega has not been updated to reflect this change. If you find yourself needing to use this then please report an issue. See also toTransformSpec.

  7. toTransformSpec :: VLSpec -> TransformSpec

    hvega Graphics.Vega.VegaLite

    This function is provided in case there is any need to inject JSON into the Vega-Lite document that hvega does not support (due to changes in the Vega-Lite specification or missing functionality in this module). If you find yourself needing to use this then please report an issue. See also fromTransformSpec.

  8. transform :: [TransformSpec] -> PropertySpec

    hvega Graphics.Vega.VegaLite

    Create a single transform from a list of transformation specifications. Note that the order of transformations can be important, especially if labels created with calculateAs, timeUnitAs, and binAs are used in other transformations. Using the functional composition pipeline idiom (as example below) allows you to provide the transformations in the order intended in a clear manner. 

    transform
. filter (FExpr "datum.year == 2010")
. calculateAs "datum.sex == 2 ? 'Female' : 'Male'" "gender"
    The supported transformations are: aggregate, binAs, calculateAs, density, filter, flatten, flattenAs, fold, foldAs, impute, joinAggregate, loess, lookup, lookupAs, lookupSelection, pivot, quantile, regression, sample, stack, timeUnitAs, and window.

  9. type ItemFormatter a = Bool -> Verbosity -> Item a -> Builder

    katip Katip

    A custom ItemFormatter for logging Items. Takes a Bool indicating whether to colorize the output, Verbosity of output, and an Item to format. See bracketFormat and jsonFormat for examples.

  10. bracketFormat :: LogItem a => ItemFormatter a

    katip Katip

    A traditional bracketed log format. Contexts and other information will be flattened out into bracketed fields. For example: 

    [2016-05-11 21:01:15][MyApp][Info][myhost.example.com][PID 1724][ThreadId 1154][main:Helpers.Logging Helpers/Logging.hs:32:7] Started
[2016-05-11 21:01:15][MyApp.confrabulation][Debug][myhost.example.com][PID 1724][ThreadId 1154][confrab_factor:42.0][main:Helpers.Logging Helpers/Logging.hs:41:9] Confrabulating widgets, with extra namespace and context
[2016-05-11 21:01:15][MyApp][Info][myhost.example.com][PID 1724][ThreadId 1154][main:Helpers.Logging Helpers/Logging.hs:43:7] Namespace and context are back to normal

Page 1351 of many | Previous | Next