Repository navigation
Document loadRegistry() behavior for exported objects - #334
Merged
Merged
Conversation
Document that loadRegistry() automatically loads objects previously exported with batchExport() into the global environment. The documentation now also notes that existing objects with the same names may be overwritten, making the behavior clearer to users.
Member
|
Thanks! I'd keep #304 open because the underlying question is whether this should happen, apart from it of course being better to document that it happens. |
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
2 participants
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.
Fixes #304
This PR updates the loadRegistry() documentation to clarify that objects previously exported with batchExport() are automatically loaded into the global environment when a registry is loaded.
It also notes that existing objects with the same names may be overwritten.
This brings the loadRegistry() documentation in line with the behavior already documented for batchExport().