You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There might be valid use cases where someone would want to use the PWFSLSmokePlots package without needing the majority of the PWFSLSmoke functionality. It also seems there is some redundancy and potential confusion about working with both of these packages, in that:
library(PWFSLSmoke)
library(PWFSLSmokePlots)
...
is loading PWFSLSmoke twice. Instead, we could instead import PWFSLSmoke and re-export a select subset of necessary functions in PWFSLSmokePlots. This would reduce redundancy in duplicate loading, and prevent cluttering up the namespace if other PWFSLSmoke functions aren't needed.
The text was updated successfully, but these errors were encountered:
There might be valid use cases where someone would want to use the
PWFSLSmokePlots
package without needing the majority of thePWFSLSmoke
functionality. It also seems there is some redundancy and potential confusion about working with both of these packages, in that:is loading
PWFSLSmoke
twice. Instead, we could instead importPWFSLSmoke
and re-export a select subset of necessary functions inPWFSLSmokePlots
. This would reduce redundancy in duplicate loading, and prevent cluttering up the namespace if otherPWFSLSmoke
functions aren't needed.The text was updated successfully, but these errors were encountered: