fix(generate): fix module component path if module is created in child folder #3066
Conversation
| @@ -58,7 +58,9 @@ module.exports = { | |||
| }, | |||
|
|
|||
| afterInstall: function (options) { | |||
| options.entity.name = path.join(this.dasherizedModuleName, this.dasherizedModuleName); | |||
| var componentPath = path.join(this.generatePath, this.dasherizedModuleName); | |||
There was a problem hiding this comment.
If you're only going to have this.dasherizedModuleName once, then you need to turn options.flat to false. The default for components is that they're in their own directory. I'd suggest using options.flat = false. And once you make that change you will also need to update your tests.
There was a problem hiding this comment.
@Brocco the dasherizedModuleName is already included in generatePath, so it was still there twice.
However, I still changed it to use options.flat = false;, without using this.dasherizedModuleName.
The outcome is the same though. Not sure why I need to change the test.
Meligy
force-pushed
the
fix/generate-module-child-folder
branch
from
b91fffe to
19753ce
Compare
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
fixes #3063