Support namespaces#79
Merged
Merged
Conversation
9e2a91e to
c878c3d
Compare
c878c3d to
b2a6b41
Compare
Closed
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.
Closes feature request #17.
Now if Temping detects you wanted to create a namespace for your model it will create it if it doesn't exist yet or use the existing one. During
.teardownit will undefine all the modules from the namespace previously created by itself.A fresh entry in the Readme:
Temping supports creating models within namespaces.
You can do this either by just including the full namespace in the name:
Or you can create the module(s) yourself:
Please note that if you create the modules yourself, Temping will NOT attempt
to undefine them when you call
Temping.teardown, it will only undefine the modulescreated by itself:
Deep namespaces are supported as well: