-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: cli options #3325
feat: cli options #3325
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3325 +/- ##
==========================================
- Coverage 95.72% 95.25% -0.47%
==========================================
Files 33 34 +1
Lines 1309 1327 +18
Branches 388 390 +2
==========================================
+ Hits 1253 1264 +11
- Misses 52 59 +7
Partials 4 4
Continue to review full report at Codecov.
|
372f3b1
to
4f42ce2
Compare
@snitin315 I think better finish this before merge it #3309 (here we finish our options) |
It should be good now. Waiting for green CI. |
I have not included |
Ideally - yes, but I think we need In theory we can move part of logic |
I will update 👍 |
5b4e85e
to
d2acaba
Compare
Done ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, let's merge it after #3309
MacOS issue, help output is short in CI. |
test/cli/cli.test.js
Outdated
@@ -586,6 +862,14 @@ describe('CLI', () => { | |||
}); | |||
|
|||
it('should generate correct cli flags', (done) => { | |||
const isMacOS = process.platform === 'darwin'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is problem? Not all output? It means we have bug somewhere...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think problem with exec nodejs/node#19218
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch 👍
}) | ||
.catch(done); | ||
}); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add test: using webpack server --config ./path/webpack.config.js
with --watch-files-paths-reset --watch-files-paths ${watchDirectory}
and do snapshot (you can set stats: false
, we will improve it late), as you can see using expect(output.exitCode).toEqual(0);
is bad testing, we need snapshot stdout and stderr, it allow use to see what we rewrite watch-files-paths
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't log which files are being watched on stderr/stdout
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though we do log for static
, added more snapshots 👍🏻
518685d
to
34c46b4
Compare
I will rebase in near future. |
@snitin315 I will finish it, WIP, also I will add test to ensure we don't lose cli args in future after adding/removing/changes our options |
CI is green ✅ |
For Bugs and Features; did you add new tests?
YES
Motivation / Use-Case
#3300 (comment)
Breaking Changes
No
Additional Info
No