plugin api

[calvinmetcalf]

currently the api is "string we never use", constructor and all the methods on the returned object get merged. Something more like "method name", constructor might be better

//old
PouchDD.plugin("mapreduce",constructor);
//idea
PouchDB.plugin("query",constructor);

a third argument could be the name of the export method

[jo]

Using the id string allows to overwrite a plugin, eg by providing a different mapreduce plugin - but I'm also unhappy with those otherwise useless strings.

And, while we're at it (and motivated by the generality of this ticket):
It would be so nice if it's possible to hook into document read and write, empowering sort of transform plugins.
Such a plugin could add timestamps for example, parse dates and so on.

With our current plugin system this is not possible because they are exclusively, meaning the last installed plugin provides the method. Maybe the plugin could just receive the old api?

[calvinmetcalf]

Well specifying the name of the method (IE query instead of MapReduce)
would have the same results, pre and post hooks would be nice, might
necessitate changing the httpadapter to use the underscore methods like
the other ones
On Feb 12, 2014 11:19 AM, "Johannes Jörg Schmidt" [email protected]
wrote:

Using the id string allows to overwrite a plugin, eg by providing a
different mapreduce plugin - but I'm also unhappy with those otherwise
useless strings.

And, while we're at it (and motivated by the generality of this ticket):
It would be so nice if it's possible to hook into document read and write,
empowering sort of transform plugins.
Such a plugin could add timestamps for example, parse dates and so on.

With our current plugin system this is not possible because they are
exclusively, meaning the last installed plugin provides the method. Maybe
the plugin could just receive the old api?

—
Reply to this email directly or view it on GitHubhttps://github.com/daleharvey/pouchdb/issues/1387#issuecomment-34884939
.

[jo]

yes, thats right.

Shouldn't it be possible to specify more than one method?

// eg
PouchDB.plugin(constructor, ["query", "find"]);
// or
PouchDB.plugin(constructor, "query", "find");

[nolanlawson]

While we're at it, #1118 is still a low-hanging fruit. Would probably really help with all the goodfirstpatch/goodstudentproject stuff.

[calvinmetcalf]

so now that the prototype one landed, we could have a new style plugin, which we just add to PouchDB.prototype