You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
lisk generate:plugin customPlugin should generate a custom plugin without error.
Actual behavior
When we run lisk generate:plugin customPlugin then it creates a file <plugin_name>_plugin.ts where nodeModulePath returns a path in invalid string format like below without double or single quotes, /lisk-sdk/commander/dist/bootstrapping/templates/lisk-template-ts/templates/plugin/src/app/plugins/plugin.t
it should be, __filename
Additionally, the following function is generated, but plugins don't emit events anymore afaik:
public get events(): string[] {
return [
// 'block:created',
// 'block:missed'
];
}
Also, this is how the load function is generated, I think channel is outdated as well.
### What was the problem?
This PR resolves#7692
### How was it solved?
Fix template per the requirements
### How was it tested?
Output checked manually
Co-authored-by: !shan <[email protected]>
Expected behavior
lisk generate:plugin customPlugin
should generate a custom plugin without error.Actual behavior
When we run
lisk generate:plugin customPlugin
then it creates a file<plugin_name>_plugin.ts
where nodeModulePath returns a path in invalid string format like below without double or single quotes,/lisk-sdk/commander/dist/bootstrapping/templates/lisk-template-ts/templates/plugin/src/app/plugins/plugin.t
it should be,
__filename
Additionally, the following function is generated, but plugins don't emit events anymore afaik:
Also, this is how the load function is generated, I think channel is outdated as well.
Probably the plugin generation needs to be generally aligned to new plugin structure for v6
Steps to reproduce
Run
lisk generate:plugin customPlugin
Which version(s) does this affect? (Environment, OS, etc...)
6.0.0-alpha.4
The text was updated successfully, but these errors were encountered: