See if we can instantiate these objects based on data we already have (the org name and package ID) instead of fetching them from GitHub via API. This can reduce a lot of repeating calls in a bunch of different methods.
Both objects have the ability to "lazy-fetch themselves" ("complete") from GitHub if a property of them that was not pre-populated is needed, so this technique can probably work and be harmless, but we should still see if it can be done and if it can actually improve performance, or are we going to call __complete in any case regardless, and then the added complexity is not worth it.
See if we can instantiate these objects based on data we already have (the org name and package ID) instead of fetching them from GitHub via API. This can reduce a lot of repeating calls in a bunch of different methods.
Both objects have the ability to "lazy-fetch themselves" ("complete") from GitHub if a property of them that was not pre-populated is needed, so this technique can probably work and be harmless, but we should still see if it can be done and if it can actually improve performance, or are we going to call
__completein any case regardless, and then the added complexity is not worth it.