Skip to content

Dynamic join: Handle palette, binning method and classes in a finer grained way #1090

@antobenve

Description

@antobenve

Currently, the dynamic join accepts 1 value per each of the following parameters:

  • palette
  • binning method
  • number of classes

It would be useful if these could change depending on the values of the filters (e.g. filter "variable"="risk" has a different set of parameters than when "variable"="probability").

This could be solved in the code of the extension by passing arrays of objects to the parameters.
Or it could be handled case by case by coding the filters out of the dynamic join and loading the dynamic join with values for palette, binning method and classes that depend on the selection of values in the filters. This approach is not preferred as it requires more code and is not usable systematically.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions