Jay Phelps
Jay Phelps
@kevinSuttle yup 😄 #84
My 2 cents: `method := { return (foo) => bar; }` defeats most of the reason people use arrow functions in fields, terseness of autobind; now it's rather verbose compared...
@ljharb I can absolutely see that argument, though fields are different as described in that their value is set at instantiation vs. methods at definition, so they're already inconsistent by...
@domenic _to me_ the equals sign by its nature inside of a class body denotes that already, but admittedly that's almost certainly because that's just how all the languages with...
Hey @bvaughn 👋 [you mentioned](https://github.com/facebook/react/issues/12014#issuecomment-537561064) the best way forward is the RFC process. Can you help direct us what the next step is from here? I saw the README mentioned...
@panrafal mostly because it's unclear how it _should_ act or when it would be useful? If you have a use case, I'm happy to add it.
@panrafal your example is basically how it worked before, which has the issue of applying the decorator to the prototype instead of the method on the instance, which is even...
Will stew on it. One minor typo: ``` js deco.call(ctx, ...args) { return deco().call(ctx, ...args); } // should be deco.call = function (ctx, ...args) { return deco().call(ctx, ...args); }; ```
Works for me: http://react.jsbin.com/baqemeqedi/edit?js,output Guessing your issue is elsewhere. Can you be more specific when you say it doesn't work? What happens instead?