Thorough error messages on bad parsing #56

Open

opened

Following up on #17 and #14, it'd be nice to brainstorm what really good parsing error messages can look like for all cases of unparseable input. We can use input given to the Socratic app as test cases probably :)

to join this conversation on GitHub. Already have an account? Sign in to comment

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