-
-
Notifications
You must be signed in to change notification settings - Fork 797
Closed
Description
Since I'm fairly new to using feathers, I was wondering the philosophy behind the pervasive use of scope in various parts of the API. I used to design APIs this way as well but lately have preferred more functional/explicit designs.
For example:
function myPlugin (options) {
return function () {
var app = this
}
}
app.configure(myPlugin({}))
vs.
function myPlugin (options) {
return function (app) {}
}
app.configure(myPlugin({}))
I understand that it would be a huge breaking change (and thus probably not realistic), but at least in this case it could be changed in a backwards compatible way (but other things like hooks and services are tricker).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels