-
Notifications
You must be signed in to change notification settings - Fork 35
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
Replace "volid" with "vol_id" throughout ORANGE #1486
base: develop
Are you sure you want to change the base?
Conversation
Test summary 3 371 files 5 194 suites 3m 54s ⏱️ Results for commit fa61437. ♻️ This comment has been updated with latest results. |
@sethrj RTR |
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.
Looks great. Do you want to do the same for univ_id, trans_id, ...? I think it would be a nice touch. Also like we have uid
in there, there are a couple of vid
for vol_id
.
Yeah I can do that too. I wasn't sure how far too go. I am thinking: surf_id, but only for local variable names. If I start changing APIs (geo.volume_id() to geo.vol_id()) the changes become more invasive. I also don't want to mess but the .jsons. |
Yes, agreed. I think it's ok (and often better?) for API names to be spelled out. In fact, I read/saw recently a guideline that said the more global an identifier's scope, the longer/more descriptive the name should be; and conversely very local variables can be very short (think |
This MR updates all files within ORANGE to use the form "vol_id" for variable names instead of "volid", for consistency with other opaque IDs such as
universe_id
,transform_id
,level_id
, etc.