Closed stafyniaksacha closed 7 years ago
Sorry to not have rebased my commit history :-1:
putting the pr in wip to address the issues in comment + fix unit tests
looks good, but is there any strong reason to switch from Prototype
to Class
paradigm ?
@ballinette the idiomatic heritage?
@balinette this is not a real paradigm switch. ES2015 class syntax does (almost) the same as util.inherits & co. We just took the opportunity of this fix to use this more up-to-date & cleaner syntax.
@benoitvidis I know it's not really a paradigm and more a syntaxic sugar.
My wonder is just that I did not notice if we had a consensus about that in the team, and I don't want to have an heterogeneous code with both class
and Prototype
syntaxes.
So at least, if everybody agrees, we should act that all new features should privilege class
syntax, and that we move gradually the actual code from Prototype
to class
.
That said, it's a more general thinkings and is not directly related to this PR in particular, so I'm not blocking it for that
Bug fixes
master
<->slaves
is now workingmaster
intoslaves
is now workingBoyscooting
kuzzle:cluster*
tag