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
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
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
andmanifest-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:
If this option is specified,
kintone-plugin-packer
searches the file name instead ofmanifest.json
and reads information about the plugin packaged.I think that the default value of it should be
manifest.json
.The text was updated successfully, but these errors were encountered: