[ 
https://issues.apache.org/jira/browse/MINIFICPP-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Gyimesi updated MINIFICPP-1860:
-------------------------------------
    Description: Readability checks of clang-tidy should be added by evaluating 
which checks should be enabled in our project and fixing the failures where 
possible then integrating it to the CI checks. If some checks should be 
enabled, but it would take way too much effort to fix them at once, they should 
be enabled in the CI and should be fixed when the problematic file is changed.  
(was: Additional checks of clang-tidy should be added by evaluating which 
checks should be enabled in our project and fixing the failures where possible 
then integrating it to the CI checks. If some checks should be enabled, but it 
would take way too much effort to fix them at once, they should be enabled in 
the CI and should be fixed when the problematic file is changed.

Checks that need to be enabled:
 * readability*
 * cppcoreguidelines*
 * performance*
 * google*

Note: This ticket can be broken down to multiple tickets if integrating the 
additional checks would be too much effort at once)

> Integrate readability clang-tidy checks in CI
> ---------------------------------------------
>
>                 Key: MINIFICPP-1860
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1860
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Gábor Gyimesi
>            Priority: Minor
>              Labels: MiNiFi-CPP-Hygiene
>
> Readability checks of clang-tidy should be added by evaluating which checks 
> should be enabled in our project and fixing the failures where possible then 
> integrating it to the CI checks. If some checks should be enabled, but it 
> would take way too much effort to fix them at once, they should be enabled in 
> the CI and should be fixed when the problematic file is changed.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to