Closed andreypopp closed 6 years ago
Hi @andreypopp I'm really keen to maintain this. My company Atlassian is using this so I have good support.
cc @bradleyayers
Nice, let's wait some time (a day) so others can respond too. Also cc @domarmstrong as he already has commit access to the repo.
@andreypopp I'm interested why you no longer use this. Do you have a different pattern that you use now?
@bradleyayers completely switched to use class instance properties:
onClick = (e) => {
...
};
typescript doesn't seem to support this yet.
@stevemao what's you npm username so I could add you there?
Sounds good @stevemao! Sadly I don't use either for quite a while now as I moved in other directions now.
Hi @andreypopp can you add @bradleyayers as well? Also would you mind adding me to npm? Thanks guys.
@stevemao what's you npm username so I could add you there?
Sorry, It's stevemao
Hi @andreypopp can you add @bradleyayers as well? Also would you mind adding me to npm?
Done
@andreypopp out of curiosity, how are you handling binding now?
I just use the standard ES7 property assignment:
foo = () => { ... }
@bradleyayers I found this to cause problems while hot reloading since methods created this way will not be hot loaded (correctly).
@baba43 Also class property methods cause problems with testing. For example you cannot use jest.spyOn
on a class property method because it's not in the prototype.
@nurbek-ab there's already tickets. Please search the issue tracker and find the solutions
As I no longer use this library it needs new maintainers.