Package
Why
When I developed a kintone plugin, I used the same manifest.json file in dev and prod (but, when using in prod, I modified the content of manifest.json file) 馃ズ
If I can specify manifest.json file name like manifest-dev.json and manifest-prod.json, I think that we can easily develop in multiple environments 馃槈
What
I want to add a new option to kintone-plugin-packer CLI: --manifest-file-name MANIFEST_FILE_NAME
Usage I imagined:
$ PLUGIN_DIR='/path/to/your/plugin_dir'
$ kintone-plugin-packer "$PLUGIN_DIR" --manifest-file-name manifest-dev.json
If this option is specified, kintone-plugin-packer searches the file name instead of manifest.json and reads information about the plugin packaged.
I think that the default value of it should be manifest.json.
Package
Why
When I developed a kintone plugin, I used the same manifest.json file in dev and prod (but, when using in prod, I modified the content of manifest.json file) 馃ズ
If I can specify manifest.json file name like
manifest-dev.jsonandmanifest-prod.json, I think that we can easily develop in multiple environments 馃槈What
I want to add a new option to
kintone-plugin-packerCLI:--manifest-file-name MANIFEST_FILE_NAMEUsage I imagined:
If this option is specified,
kintone-plugin-packersearches the file name instead ofmanifest.jsonand reads information about the plugin packaged.I think that the default value of it should be
manifest.json.