You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To simplify our lives, let's assume that files are Ruby if they aren't recognized by any other parser (for now, that's just .erb). This will eliminate encountering "unknown file type" errors.
If assuming Ruby fails, we'll have to encourage people to use the include / exclude globs in their configs to handle other types of files.
We could assume a file without an extension is an executable, check to see if it looks like a Ruby executable, and ignore it if it's not. @thegedge prefers being explicit, but can understand that a larger repo may have built up a lot of executable files, many of which may not be Ruby.
The text was updated successfully, but these errors were encountered:
We have a PR in progress in packwerk to support custom parsers. Once this merges and we release it, another approach here is that you could define a custom parser that inherits from the existing ruby parser and matches all files except ruby. That way users could opt into this behavior without affecting current behavior.
To simplify our lives, let's assume that files are Ruby if they aren't recognized by any other parser (for now, that's just .erb). This will eliminate encountering "unknown file type" errors.
If assuming Ruby fails, we'll have to encourage people to use the include / exclude globs in their configs to handle other types of files.
We could assume a file without an extension is an executable, check to see if it looks like a Ruby executable, and ignore it if it's not. @thegedge prefers being explicit, but can understand that a larger repo may have built up a lot of executable files, many of which may not be Ruby.
The text was updated successfully, but these errors were encountered: