Feature Request: Exit Code should reflect if changes are required on a new paramter like --check
See original GitHub issueAs the title says. I would like to add this to a ci “linting” pipeline, therefore setting the rturn code to something other than 0 if there should be new typings added or removed would be nice.
I would suggest something like typesync --check
which behaves like --dry
but alters the return code.
or you paramerize the dry parameter like typesync --dry=fail
Thank you!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Add integer exit code for 'az deployment group what-if' command
The exit code should reflect the execution status of the what-if command itself. If users need the status of the deployment change preview,...
Read more >About the enhanced conversions for web tag diagnostics report
Enhanced conversions is a feature that can improve the accuracy of your conversion measurement. It supplements the existing conversion tags by allowing ...
Read more >Updates and breaking changes - Azure - Microsoft Learn
Learn about changes to the Microsoft identity platform that can impact your application.
Read more >Modify the values of an Amazon RDS DB parameter group
To change an RDS DB instance configuration, you must change the parameter values of the DB parameter group for your RDS DB instance....
Read more >NG0100: Expression has changed after it was checked - Angular
This error commonly occurs when you've added template expressions or have begun to implement lifecycle hooks like ngAfterViewInit or ngOnChanges . It is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Released in 0.9 👍
This basically enforces the type definitions to be present at all times within the package.json.
Scenario: One developer forgets to “typesync” after adding a new dependency, pushes. The next developer pulls the changes, and then executes
npm install & typesync
. The expectation would be, that he does not have any outstanding files, that he has to commit.Adding a step to the CI, could enforce a typesynced-package.json at all times