Skip to content

clientside callbacks mutate arguments in place - but the docs don't mention this #1819

Open
@JonThom

Description

@JonThom

As mentioned in #1040 clientside callbacks differ from their python counterparts by not serializing and de-serializing props, which instead get mutated in place.

Given that this is not explained in the docs, the errors that result from mutating component props in place are extremely cryptic (e.g. unexpected firing of other callbacks, or components throwing all kinds of errors).

It would have saved me two days of debugging time if there had been a line or two about this to the docs, and I would suggest adding it ASAP to spare others the same!
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions