Move plugin configs to config/plugins (#1907)

This changes the instance system structure so that all the
plugin-specific configs are organized under
`config/plugins/$OWNER/$NAME` instead of `config/$OWNER/$NAME`. I think
this is a somewhat clearer structure; since `config/` will hold other
files (e.g. `weights.json` or `params.json`), I think it's cleaner if
everything plugin-specific is under it's own clearly scoped folder. This
avoids potential confusion if we ever have plugins with very
generic-named organizations, e.g. "config".

Test plan: The test instance has been updated, and the sharness test
loading still works.
This commit is contained in:
Dandelion Mané 2020-06-30 11:24:23 -07:00 committed by GitHub
parent 7ab3a74c3a
commit 811bf32968
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 1 additions and 1 deletions

View File

@ -50,7 +50,7 @@ export function pluginDirectoryContext(
pluginName: string
): PluginDirectoryContext {
const cacheDir = makePluginDir(baseDir, ["cache"], pluginName);
const configDir = makePluginDir(baseDir, ["config"], pluginName);
const configDir = makePluginDir(baseDir, ["config", "plugins"], pluginName);
return {
configDirectory() {
return configDir;