Ensured that the namespace for generated code is the same as the script by default #161
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.
Previously when creating a new collection, the
Namespacefield that the collection applies to its generated scripts would default to the namespace prefix, instead of using the same namespace as the collection script itself. Given that by default it places the generated script in the same folder as the as the collection itself, it should also use the same namespace by default, with the option to set it to something else if you prefer.