On file-system level we have a more sophisticated structure than we want on a namespace-level. Even though this is a really old post it describes the issue (that still persists til today) pretty good.
When creating new files we do not want the namepsace to match the file-system structure, e.g.
namespace MyApp.MyModule.Filesystem.Export.Csv.Logic
but instead we would like
namespace MyApp.MyModule
when creating a new file in .\proj-dir\MyModule\Filesystem\Csv\Logic\
I see that the needs to limit the namespace-levels might differ so one would need an option to set a specfic / fixed level.
Now I am curious if you can see such a feature to be added to this extension? If we can agree on something I would gladly provide a corresponding PR.
Or is this request out-of-scope for this project?
Anyways: a nice extension. Thanks a lot for sharing.
Optional limitation of namespace parts
On file-system level we have a more sophisticated structure than we want on a namespace-level. Even though this is a really old post it describes the issue (that still persists til today) pretty good. When creating new files we do not want the namepsace to match the file-system structure, e.g.
namespace MyApp.MyModule.Filesystem.Export.Csv.Logic
but instead we would likenamespace MyApp.MyModule
when creating a new file in.\proj-dir\MyModule\Filesystem\Csv\Logic\
I see that the needs to limit the namespace-levels might differ so one would need an option to set a specfic / fixed level.
Now I am curious if you can see such a feature to be added to this extension? If we can agree on something I would gladly provide a corresponding PR.
Or is this request out-of-scope for this project? Anyways: a nice extension. Thanks a lot for sharing.