Skip to content

better algorithm/API for distinguishing mapping vs setting? #21

@rpruim

Description

@rpruim

The current algorithm considers anything that is a name of the data to be mapped and all other things to be set. This doesn't allow for on-the-fly calculations like

gf_point(y ~ x, data = Foo, color = y > x)

The culprit is the following code chunk:

data.frame(role = names(res),
                    var = unlist(res),
                    map = unlist(res) %in% data_names)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions