Ability to define multiple static directories in plugin system

[julianlam]

... for my own nefarious purposes, of course. 👽

[cnvo]

👍 Muahaha.

[julianlam]

Important!

This introduces a couple of backwards-compatible change to plugins:

1. If staticDir is defined, it will be mapped to /plugins/{plugin-id}, same as before
2. If staticDirs is defined, it is an object that specifies mappings, e.g. { 'test': 'assets/css' } will map /plugins/test to /node_modules/{yourPlugin}/assets/css
3. If staticDir is defined, any entries in css will be mapped to /plugins/{plugin-id}/{file}, same as before
4. If staticDir is not defined, any entries in css will be mapped 1:1 with a previously defined staticDir. e.g. A css file in /node_modules/{yourPlugin}/assets/css would be defined: ['/test/style.css']

---

So, plugins as they are will continue to work, but throw deprecation warnings now. They will stop working for v0.5.

[cnvo]

Thanks a ton for the reference!

On Sun, Feb 2, 2014 at 1:08 PM, Julian Lam notifications@github.com wrote:

Important!

This introduces a couple of backwards-compatible change to plugins:

1. If staticDir is defined, it will be mapped to /plugins/{plugin-id}, same
   as before
2. If staticDirs is defined, it is an object that specifies mappings,
   e.g. { 'test': 'assets/css' } will map /plugins/test to
   /node_modules/{yourPlugin}/assets/css
3. If staticDir is defined, any entries in css will be mapped to
   /plugins/{plugin-id}/{file}, same as before
4. If staticDir is not defined, any entries in css will be mapped
   1:1 with a previously defined staticDir. e.g. A css file in
   /node_modules/{yourPlugin}/assets/css would be defined:
   ['/test/style.css']

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/926#issuecomment-33907196
.

[julianlam]

👍