-
Notifications
You must be signed in to change notification settings - Fork 45
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
Add Historical Industry Value Added Figures to historical.mif #396
Add Historical Industry Value Added Figures to historical.mif #396
Conversation
Not sure if putting read and convert into one file is a problem (UNIDO.R as opposed to creating two files readUNIDO.R and convertUNIDO.R) @LaviniaBaumstark can you comment on this? |
Thought experiment: pick a random R function (not from within the pik-piam sphere) and tell me the name of the source file it was is. |
69af07e
to
442f5ff
Compare
No unexpected differences in output.
|
442f5ff
to
de92737
Compare
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.
please, split UNIDO.R into readUNIDO.R and ConvertUNIDO.R, otherwise some functionality of madrat functions will get lost
Also if most of the functionality also works for your version, the rule is different and all madrat function rely on this. I cannot guarantee (and also not test) that all madrat functionality is working for your version. If everyone follows the rules, clear interfaces are provided. In addition, following the rules enables other developer to understand your code easier. |
There is no functionality in madrat that depends on either the name of source code files, or the number of functions defined inside source code files. There can't be, because that information is simply not available to the madrat package. |
why do you want to make it different? |
Because |
We checked back with the rest of the RSE group. Michaja, you are right, there is no technical requirement to write separate functions. Splitting read and convert into functions with the same name is the recommended way to do it, but not a convention we enforce. We recommend it as a convention, because it helps newcomers with finding specific functionality fast and getting a quick overview of what the R functions of an mr package do. So if you insist on keeping it that way, this won't block this PR. |
de92737
to
8bee547
Compare
Not sure whether "finding specific functionality fast" is the right term for scrolling through a list of 267 files whose names start all with one of three words … |
8bee547
to
fa1dcb8
Compare
Test runs pending …