Roadmap

v1

Released June 23, 2014

• Get it awesome
• Get it working
• Figure out extension API
• Prevent base prototypes from being extended
• Figure out how plugins and bundles will be created and installed
• Figure out whether to keep the name extensions or go back to plugins (done, see Glossary)
• Have Chainy.prototype.create() keep the parent's extensions
• Rip out plugins from main repo
• Finished publishing ripped out plugins
• Create the Chainy CLI
  • Create plugins for Chainy for interacting with the CLI
  • Figure out whether to publish chainy-autoload, or chainy-core
    • Most probably autoload can be a plugin, that chainy uses, with chainy using chainy-core
  • Figure out if the overhead of having the CLI inside chainy is worth it, as the CLI will be installed for every module, when it doesn't have to be. Perhaps best to publish chainy-cli, that then exposes chainy (it's not, renamed CLI in docs to chainy-cli)
• Finish the documentation

v1.x

• Be able to require non-chainy plugins and use them as plugins: #14
• Support more liberal extension names: #11
• Allow for "action/?" extensions to do without the chain data argument while still receiving supplied arguments: #17

v2

There will hopefully be no v2.0. With the Chainy core becoming finalised and innovations continuing over in plugins instead.

Anytime

• Create a website

Plugin Requests

• ajax plugin using request or some xhr clone
• jquery equiv of .end() for conditional chains