Skip to content
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

exitOnIssue flag #97

Closed
wants to merge 2 commits into from
Closed

Conversation

tay1orjones
Copy link

Should resolve #88 and enable the CLI to exit with code 1 for CI build tools, etc

Includes documentation/usage updates

Let me know what you think @GertjanReynaert 🙂

@codecov-io
Copy link

codecov-io commented May 24, 2017

Codecov Report

Merging #97 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #97   +/-   ##
=======================================
  Coverage   96.77%   96.77%           
=======================================
  Files           2        2           
  Lines          31       31           
  Branches        7        7           
=======================================
  Hits           30       30           
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6ae625d...f70f325. Read the comment docs.

@bf
Copy link

bf commented May 29, 2017

Please merge this, the package becomes very useful now.

@ctumolosus
Copy link

@GertjanReynaert do you have some time to review this PR? Would love to see this feature released.

Copy link
Owner

@GertjanReynaert GertjanReynaert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @tay1orjones, first of all, apologies for the late response.

Are you still up to finishing this pr? If not, no problem, just let me know.

Apart from the rebase that needs to happen, I have a few remarks that are written down in the review I did.

@@ -174,6 +174,12 @@ these messages.
afterReporting: () => {},
}
```
- `exitOnIssue` (optional, default: `true`)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you change this default to false since that's the default you used here

@@ -40,6 +41,7 @@ export default ({
duplicateIds.forEach(id => {
console.log(' ', `Duplicate message id: ${red(id)}`);
});
exitOnIssue ? process.exitCode = 1 : null;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move this line to the line after this line in the outputDuplicateKeys core method? Since the printer methods should only be concerned about printing to the console, it doesn't really fit here.

@@ -48,7 +50,7 @@ export default ({

printLanguageReport: langResults => {
header(`Maintaining ${yellow(langResults.languageFilename)}:`);
printResults({ ...langResults.report, sortKeys });
printResults({ ...langResults.report, sortKeys, exitOnIssue });
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move this exitOnIssue implementation to this line in the reportLanguage core method? Same reason as the previous comment.

@amakhrov
Copy link

Any plans to move forward with that?

@pierreferry
Copy link

What are the blocking points for the PR atm ? That would be a great feature for me !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
7 participants