Skip to content

Transformation results should be memoized on encoding instead of on marker #27

@jheeffer

Description

@jheeffer

This makes encodings less coupled to the marker. Encodings would have a specific place to "pick up", an observable, where to get input data from. This can be set to a marker, which saves a reference to the previous transformation's result, or a local dataframe in case of a stand-alone encoding.

This transformInputs place can also be useful as it may be used by other helper methods in the encoding, like limits in trail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions