Skip to content

Provide actual messages in JS errors #40756

@sagudev

Description

@sagudev

Now that each error variant accepts Option<String> (#39053), we should start to write actually error messages instead of passing None.

OFF-TOPIC: Should we accept Cow rather than string? Or maybe even create JSString directly? (probably not).

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