ES6 class pattern about pokemon-go-node-api HOT 4 CLOSED

Send a pull request with your suggestions :) open source! What specifically would be better in this code using the class feature?

I'd personally not suggest to ever use classes, but that's my preference.

from pokemon-go-node-api.

I'll throw in my 2 cents: typescript and ES6 classes are great, but considering the nature of the project and the fact that at any moment the endpoints, protocols, etc. could change, I think that whatever design patterns the contributors are comfortable with are the best ones to go with. It seems like at this point the big hurdle is reading data through the buffer correctly and reliably.

from pokemon-go-node-api.

Usually I prefer to use pure node.js callback with an OOP like structure

from pokemon-go-node-api.

yield, generators, async, await, promise, es6 classes, node-fetch is my preference

And also the use of async-classes

from pokemon-go-node-api.