We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forjj through goforjj use <plugin>.yaml: /plugin: <value> to connect to the proper socket.
<plugin>.yaml: /plugin: <value>
If we created a new plugin with a wrong name, the cli.go is generated and will never be updated if we do not remove it, before a go generate
go generate
So, even if we change <plugin>.yaml, forjj will take care of it, but not the plugin until we change manually the cli.go in load_plugin_def function
<plugin>.yaml
load_plugin_def
We need forjj and plugins to be more coherent. The rule should be:
<plugin>.yaml: /runtime/serviice/socket:<value>
forjj
plugin
The text was updated successfully, but these errors were encountered:
No branches or pull requests
forjj through goforjj use
<plugin>.yaml: /plugin: <value>
to connect to the proper socket.If we created a new plugin with a wrong name, the cli.go is generated and will never be updated if we do not remove it, before a
go generate
So, even if we change
<plugin>.yaml
, forjj will take care of it, but not the plugin until we change manually the cli.go inload_plugin_def
functionWe need forjj and plugins to be more coherent.
The rule should be:
<plugin>.yaml: /runtime/serviice/socket:<value>
is set, use it in bothforjj
and theplugin
.<plugin>.yaml: /plugin: <value>
in bothforjj
and theplugin
.The text was updated successfully, but these errors were encountered: