8000 Address bad karma opts by lread · Pull Request #1 · ingesolvoll/doo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Address bad karma opts #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 2, 2021

Conversation

lread
Copy link
@lread lread commented Jan 26, 2021

Starting with Karma v6:

Karma is more strict and will error out if unknown option or argument is passed to CLI.

It turns out that doo has been passing bad opts to karma, but karma just used to grin and take it. No longer.

This change adds a check to see if doo has been asked to target karma, and if so, only passes config.
Doo was formerly passing config and compiled JavaScript to karma, karma does not expect compiled JavaScript.

Change tested with Karma v5 and v6 in rewrite-clj which uses cljs-test-runner (and hence this fork of doo) to target node, chrome-headless (via karma) and planck.

I tried running unit test for doo via lein test but it appears they are in a broken state?

lread added 3 commits January 26, 2021 12:18
Karma v6 fails on invalid command line args.

Doo was passing opts + compiled js to karma when it should have only
been passing opts.
This will make it less confusing when clicking on github repo link
from clojars.
@ingesolvoll
Copy link
Owner

Hi, thanks for submitting!

This seems pretty simple and low risk to me, how sure are you that this won't break anything?

A short description of the PR would be helpful, like:

  • What specific problem is it solving
  • Are there compatibility issues in the APIs introduced?
  • What versions did you test?

@lread
Copy link
Author
lread commented Jan 29, 2021

This seems pretty simple and low risk to me, how sure are you that this won't break anything?

I think we are good. If something unexpected comes up after release, I'll help to address.

@lread
Copy link
Author
lread commented Feb 1, 2021

@ingesolvoll, please let me know if there is anything else you'd like me to do before you merge and deploy.

@ingesolvoll ingesolvoll merged commit 0645760 into ingesolvoll:master Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0