v6 CLI arg verification breaks extra args parsing

Hello, currently karma CLI doesn’t allow explicit test files as arg so we’re passing them at the end and parse them out in karma.conf.js and v6 breaks it so I’m essentially asking if:

1. Karma CLI can support explicit test files passed in as args OR
2. Make strict mode be optional

I understand that this is not previously a feature but a lot of stack overflow answers seem to point to this mechanism being the workaround to further modify karma conf using CLI arg.

The way we’re calling it is essentially karma start karma.conf.js [testFiles...]

Thanks!

[devoto13]

@paulie4 Thanks for sharing!

Looking at this library I start to think that maybe we should provide an API for a plugin to register their CLI arguments. This way there will be one standard mechanism and as a bonus, we can include parameters provided by plugins in the karma --help output. Which will be a neat feature.

The solution from https://github.com/karma-runner/karma/issues/3625#issuecomment-766438809 will not work for karma-jasmine-spec-tags without extra changes on their side. At this point, I lean towards temporarily reverting the strict parameters validation and gathering more feedback on the custom parameter use cases. So we can design a mechanism, which works for everybody.

[devoto13]

So I think the best solution would be to introduce --client-args flag for karma run command, then add a warning that the behavior of karma run -- my-arg form is going to change and point to the new --client-args flag. Allow passing arbitrary arguments after -- on any karma command. If this sounds like a good plan, I’ll work on the PR in the coming days.