dmod: Make more robust when used outside default folders #13
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.
The snippet expansion is now split into two distinct parts: the namespace and the module name.
The namespace expansion looks for a
lib|test|spec
folder and uses any folder below that as the namespace, joined by dots. If nolib|test|spec
folder can be found, no namespace will be generated.The module name is generated through the
TM_FILENAME_BASE
, and is basically the same as it was before. But this allows us to generate adefmodule Config
module inconfig/config.exs
.Before
Expanding
dmod
inlib/foo/bar/baz.exs
would result in:But expanding
dmod
inconfig/foo/bar/baz.exs
would result in:Which is certainly unexpected.
After
Expanding
dmod
inlib/foo/bar/baz.exs
would result in:And expanding
dmod
inconfig/foo/bar/baz.exs
would result in:Which is not as nice as the
lib
version above but at least a usable module name. 🙂