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
Remove deprecated exists
API in favor of fillDescriptions
in SiPixelQualityESProducer
#40135
Merged
cmsbuild
merged 1 commit into
cms-sw:master
from
CMSTrackerDPG:SiPixelQualityESProducer_fillDescriptions-12_6_X
Nov 28, 2022
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 changes: 1 addition & 4 deletions
5
CalibTracker/SiPixelESProducers/python/SiPixelQualityESProducer_cfi.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole section above could be replaced by a loop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was also a literal copy-paste from the
edmPythonConfigToCppValidation
executable with some changes in variable names to make them a bit more descriptive. I am not actually sure what you want to put in the loop. If you are referring to the twodefault_ps.push_back(temp);
calls, therecord
parameter differs in the two instances and introducing someif
statements would seem less elegant that this implementation proposed byedmPythonConfigToCppValidation
. This I leave as is for now unless I misunderstood what you meant.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need of an
if
, you can just declare an array with record names and loop over it with range-based loop while doing thepush_back
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need of an
if
, you can just declare an array with record names and loop over it with range-based loop while doing thepush_back
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be honest, I find the readability of the code dumped by
edmPythonConfigToCppValidation
better than having it in a loop form because it resembles more the layout of the final cfi file. Unless there is some performance issue with the current implementation, which I doubt, I leave it as is :) If it bothers you that much, the branch is under the CMSTrackerDPG organization ;)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we have different taste in readability. Anyway It does not bother me at all, it was said upfront it's "cosmetics".