Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Include file type in issues created from exceptions #39

Open
izuzak opened this issue Feb 13, 2015 · 2 comments
Open

Include file type in issues created from exceptions #39

izuzak opened this issue Feb 13, 2015 · 2 comments

Comments

@izuzak
Copy link
Contributor

izuzak commented Feb 13, 2015

Example issue where this would have been helpful: atom/atom#5472 (see atom/atom#5472 (comment)).

Perhaps we could include the extension of the file and the grammar which was used (just like in the status bar)?

EDIT: might be helpful to include some other file-related info, such as the total size, the number of lines, longest line, permissions, encoding?

@kevinsawicki
Copy link
Contributor

For atom/atom#5472, first-mate could definitely include the grammar path in the exception message to make it easier to know which grammar has a bad pattern.

@forivall
Copy link

forivall commented Mar 3, 2016

For those looking to validate grammars, I made a quick and dirty checker at https://www.npmjs.com/package/seaworthy, which just loads the grammar and then tries to parse all of the patterns.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants