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

engine: keep the same lint with tiflow repo #379

Merged
merged 5 commits into from
May 11, 2022

Conversation

amyangfei
Copy link
Collaborator

@amyangfei amyangfei commented May 11, 2022

Since pingcap/tiflow enables two more CI linters to check exported variable/function comments. Dataflow engine is better to follow the same rule.

  • This PR enables EXC0012 and EXC0014 for part of packages
  • These two linters for lib, jobmaster, and executor/worker will be enabled in another PR

ref: pingcap/tiflow#5352

@amyangfei amyangfei force-pushed the keep-the-same-lint-as-tiflow branch from 1d69be8 to 73a711a Compare May 11, 2022 08:39
@codecov-commenter
Copy link

Codecov Report

Merging #379 (73a711a) into master (a2980f0) will decrease coverage by 0.0727%.
The diff coverage is 50.0000%.

@@               Coverage Diff                @@
##             master       #379        +/-   ##
================================================
- Coverage   54.9763%   54.9036%   -0.0728%     
================================================
  Files           135        135                
  Lines         10590      10584         -6     
================================================
- Hits           5822       5811        -11     
- Misses         4317       4320         +3     
- Partials        451        453         +2     

amyangfei and others added 3 commits May 11, 2022 18:36
Co-authored-by: maxshuang <huangguohao@pingcap.com>
Co-authored-by: maxshuang <huangguohao@pingcap.com>
@amyangfei amyangfei merged commit a22bef5 into hanfei1991:master May 11, 2022
@amyangfei amyangfei deleted the keep-the-same-lint-as-tiflow branch May 11, 2022 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ptal Could you please take a look?
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants