A proposed function to provide base::getNamespaceExports() for {box}#369
Open
A proposed function to provide base::getNamespaceExports() for {box}#369
base::getNamespaceExports() for {box}#369Conversation
Get module exports
Merged
3 tasks
Author
|
Hi, @klmr , is this a safe way to do this? |
Owner
|
Hi @radbasa Apologies, I haven’t had time yet to look at the proposal but I promise I’ll get to it eventually. At any rate thanks a lot for the PR, it’s highly appreciated! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a proposed solution to provide similar functionality to
base::getNamespaceExports().The implementation is largely a subset of
box::use(),box:::use_one(),box:::load_and_register()with the loading packages/modules/functions into the environment removed.