Thanks for the review @shadowhand

I have cleaned this up based on your suggestions.

Any thoughts on this one @mnapoli ?

Hey, sorry for the delay. Big PRs are always harder to merge than simple ones 😬

There was a misunderstanding on my side, that's my fault. In the initial conversation, you mentioned 2 changes:

In the current implementation, when we pass the --path flag, it must be passed before the handler file.

When running Bref with Serverless, the handler file has the -f flag. I could add this to the non-Serverless bref-local script to ensure consistency in how functions are invoked locally regardless of whether we are using Serverless, CDK or Terraform.

I only considered the first suggestion, and I think solving this "bug" is great.

Regarding the second proposition, I'm not convinced. Yes, having consistency in flags could be good in theory, but:

• those that use bref-local are usually not using Serverless Framework, so consistency with SF is not important
• the SF API sucks IMO. I've been passing those -f function-name arguments since forever and I hate it

The Node world has a poor ecosystem for dealing with CLI flags and arguments. That's why they almost always use options (bref-local --option=x) instead of arguments (bref-local x). In the PHP world, the Symfony Console has set an invaluable precedent with very strong commands/sub-commands/args/options concepts, which always work well. I think we should take advantage of this for a better UX.

So here's why I'm really hesitant to merge this:

• This PR changes the public API (even with backward compatibility), which is something we don't want to do without good reason
• The SF API is worse, and aligning on this for consistency is not important and brings a worse UX for Bref users
• This PR changes logic that's not heavily covered by tests, so I'm always even more hesitant to merge

All this is adding up. I'm sorry because of the time you invested in the PR, but I don't think it's worth merging in its current state 😬 Hope that makes sense.

I think the best option would be to only solve the 1st problem (--path should work if passed before or after arguments), if that's possible?

Thanks for the detailed feedback. @mnapoli

I'm not sure if it is possible to solve just the first issue using getopt but I can certainly take a look to see how feasible it is without any dependencies. I'll do some investigating and hopefully get some changes up for your consideration. Thanks 🙏

Closing inactive PRs, feel free to reopen.