Skip to content

Should plotly export require data be a vector? #319

@benkamphaus

Description

@benkamphaus

First, thanks for making Clay! I'm using it a ton and hope to be at a point where I can start contributing more to the community or project soon!

I recently started running into some plotly export issues rendering pdf via the quarto path, where I've gotten failures on this line due to not having a vector / associative data structure:

(let [data (update data 0 dissoc :r :fill :mode :theta :z :lon :lat :width)

i.e. (update data 0 ... ) expects to act on a vector, versus e.g. nth based de-structuring or some sequence oriented way to apply the dissoc to the first element only.

Other paths seem happy to render through with seq-able or nth-able. I've wrapped plotting routines in my own code now where they proactively vec or mapv etc. to get ahead of this, so have a workaround in the meantime. But wanted to surface as I wasn't sure if this was intended or happenstance.

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