Looks good but would be a bit cleaner to use the same pattern as DataDirFlag to set the default
I started to do this, and stopped for two reasons. One was to limit the changes (as much as possible) within the //begin and //end tags. I suspect those might be some sort of automated merging indicator for the PluGeth people.
The other was that the setDataDir() method has to do with the NodeConfig, but the plugin initialization happens before that rest of the NodeConfig is setup.
> Looks good but would be a bit cleaner to use the same pattern as `DataDirFlag` to set the default
I started to do this, and stopped for two reasons. One was to limit the changes (as much as possible) within the `//begin` and `//end` tags. I suspect those might be some sort of automated merging indicator for the PluGeth people.
The other was that the setDataDir() method has to do with the NodeConfig, but the plugin initialization happens before that rest of the NodeConfig is setup.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add a new flag,
--pluginsdir, for setting the directory where plugins are stored. The default remains$datadir/plugins.Looks good but would be a bit cleaner to use the same pattern as
DataDirFlagto set the defaultI started to do this, and stopped for two reasons. One was to limit the changes (as much as possible) within the
//beginand//endtags. I suspect those might be some sort of automated merging indicator for the PluGeth people.The other was that the setDataDir() method has to do with the NodeConfig, but the plugin initialization happens before that rest of the NodeConfig is setup.