Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ToDo] Improve error messaging in jess package #14

Open
matthew-dean opened this issue Jan 24, 2021 · 1 comment
Open

[ToDo] Improve error messaging in jess package #14

matthew-dean opened this issue Jan 24, 2021 · 1 comment
Labels
help wanted Extra attention is needed todo

Comments

@matthew-dean
Copy link
Member

matthew-dean commented Jan 24, 2021

For the Jess CLI, we can receive errors with file, line, and column information. So we should export a formatted table with said information in a way that VSCode / other IDEs can directly link to said line / column.

Note: we can expect to receive an array of errors in the case of errors during tokenization / parsing, so we should support outputting multiple lines. ESLint is a good example of outputting "tables" of error messages.

@matthew-dean matthew-dean added help wanted Extra attention is needed todo labels Jan 24, 2021
@matthew-dean matthew-dean changed the title [ToDo] Format tokenizing / parsing errors like ESLint [ToDo] Improve error messaging Jan 31, 2021
@matthew-dean
Copy link
Member Author

Note: the chalk module should be used (and is installed) to make some nice color formatting of error / warning / success messages.

@matthew-dean matthew-dean changed the title [ToDo] Improve error messaging [ToDo] Improve error messaging in jess package Jan 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed todo
Projects
None yet
Development

No branches or pull requests

1 participant