viperet / vscode-magento-wizard

Helps develop Magento 2 extensions using VSCode
36 stars 16 forks source link

Magento Wizard can’t default content new file #29

Open SmartLJM opened 3 years ago

SmartLJM commented 3 years ago

create new extension can works 1 image but Magento Wizard can’t default content when i create new file,like: image image it's empty! this is my setting image so,what's the problem?

viperet commented 3 years ago

@SmartLJM can you open 'Output' tab, switch to 'MagentoWizard' channel, and post log info from it here (after you try to create a block, or invoke some MagentoWizard command from F1 menu). It should look like:

PHP 7.0.33 (cli) (built: Aug 14 2019 16:33:54) ( NTS )
Found Magento root at /Users/viperet/Documents/Work/Magento
 - Modules: 151
 - Themes: 11
 - Blocks: 3344
Running '/Applications/MAMP/bin/php/php7.0.33/bin/php bin/magento --no-ansi' in /Users/viperet/Documents/Work/Magento
SmartLJM commented 3 years ago

image well,does it can't find registration file?that's odd,should i do something special?

jcellon commented 3 years ago

Same issue here, nothing defaults or any boilerplate code when creating a class. Was this issue fixed?

viperet commented 3 years ago

@jcellon can you check debug output? Open 'Output' tab, switch to 'MagentoWizard' channel, and post log info from it here (after you try to create a block, or invoke some MagentoWizard command from F1 menu). Usually, that means you don't have PHP executable available, it is used to get info about Magento modules and themes from registration.php files. But for @SmartLJM it is something else, I can't yet reproduce this problem.

jcellon commented 3 years ago

@viperet Thanks for the follow up. I did your instructions like: switch to the 'output tab' and when I do F1 and try to inject dependency from the MagentoWizard nothing comes up. But looking into the Runtime Status I get: File not in the workspace (not saved yet?) I could move this comment to a new issue if that works

viperet commented 3 years ago

@jcellon yes please create a separate issue. Try to create a file, for example etc/di.xml in some module and post log from the output tab in that issue.