[Common] TPC PID: Cleanup of CCDB accessors #21128
Annotations
10 errors and 2 notices
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L132
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L131
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L121
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L118
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L117
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L1
Name of a workflow file must match the name of the main struct in it (without the PWG prefix). (Class implementation files should be in "Core" directories.)
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L477
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L474
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L404
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
Common/TableProducer/PID/pidTPC.cxx#L401
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests
To tolerate certain issues in a directory, add a line with the test name in "o2linter_config".
|
|
Run tests
Exceptionally, you can disable a test for a line by adding a comment with "o2-linter: disable=" followed by the name of the test and parentheses with a reason for the exception.
|
Loading