Skip to content
This repository was archived by the owner on Jan 7, 2026. It is now read-only.
This repository was archived by the owner on Jan 7, 2026. It is now read-only.

feature: include origin with penpot events #225

@mdbenito

Description

@mdbenito

Is your feature request related to a problem? Please describe.

I would like to know whether certain events:

  • originate from the user
  • are "derived", i.e. are the (in)direct consequence of a user action.
  • are "synthetic", e.g. originate at a plugin

The cases of interest to me are:

  1. selection events: did the user select the shape, or was it me?
  2. content save events: did the user save the file, or was it an external trigger (if that's possible)

Describe the solution you'd like.

selectionchange events include an origin in the payload. contentsave events include a type in the payload, etc.

Describe alternatives you've considered.

For 1. I can hack my way around with some sloppy global state 🙈 , but it seems nicer to have an "origin" attached to events IMO.

For 2. I would like to know whether another client triggered a file update (although admittedly, this might be a bit of an XY problem)

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions