jbolda / changesets Goto Github PK

This is a tracking issue for the objectives required for the PR as discussed in changesets#310.

TODO:

• Allow config.json to accept package options where the user can specify custom commands to be run during each "lifecycle"
  • This will allow someone to specify a script listed in their package.json if they want to add functionality to run on top of the standard functionality
  • This will also allow someone to use a completely custom command in the case of languages other than javascript. Someone can specify a command that runs and increments a package version in the language of their choosing, e.g. cargo release.
• Pass the config options with the existing hardcoded defaults as an optional default.
  • This will maintain backwards compatibility and then allow someone to specify a custom command pulled from the previous bullet point.
• Update the get-workspaces package to look for packages that created when using languages other than javascript. (Likely the greatest effort.) This is now actually in a separate repository.
  • Creating a plugin system is the easy answer, but we are looking to start with built in and hopefully make it extensible enough that we don't need a plugin system.