Pass the file path to the formatter

[ngan]

What are you trying to accomplish?

I can't get the check to finish on our repo because there are parsing errors (on both packwerk and our code). But when it errors, I can't tell where it's at. I've been adding puts to the cli. While I was there, I thought it'd make sense for the cli to pass along the path to the formatter in case someone wants to make a document-style formatter.

What approach did you choose and why?

This is similar to how RSpec (and others) formatter works.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code refactor (non-breaking change that doesn't add functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• It is safe to simply rollback this change.

[tomstuart]

Thank you for your contribution @ngan! It’s a good idea but I’m inclined not to merge it yet because we don’t know whether anyone is planning to contribute a formatter that needs this information, and in the meantime it’s not serving any purpose in the codebase. Do you have any immediate plans to use it?

[ngan]

because we don’t know whether anyone is planning to contribute a formatter that needs this information

That's fair! I was running into parsing errors and was trying to find the cleanest place to puts the error info (line num, etc) and I thought it was best in the formatter.

I'll take a crack at this: #19 since we actually need it...

[tomstuart]

Cool, thanks. I’ll close this PR for now to help us with triage, but we can reopen later if you need it to be merged for whatever comes out of #19.