Skip to content

pretty errors and messages #38

@alemidev

Description

@alemidev

Make sure every action spits out proper errors (and visible to the user! not in console). Also properly separate from debug errors and user errors: a requested action that fails needs to notify the user! failing to draw an user cursor because out of bounds should just go in console.

All user interactions must end with either a clearly visible state change, or a prompt!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    documented

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions