Dmitry Shpak
Dmitry Shpak
> What I can see are people mixing disabledClearable with required and its validation. @povilass There can be some confusion, true. But in terms of UX it makes perfect sense:...
👍 for the issue, although I'm not ready to jump into contributing. hope my comment will bring it up
actually, I came here not because of cloning, but because of `merge` and `assoc`. my naive initial thought was _why is `for...in` used, and not spreading?_, but I guess that...
> For these casas of shallow cloning (assoc, merge), would you suggest to replace [for...in](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...in) with {...obj} or Object.assign({}, obj)? So, we have ```js function assoc(key, value, obj) { return...
The only issue that remains is that it won't copy inherited rules anymore. For me, it sounds a-ok, I don't really dig into inherited properties usually. And it seems like...
@semmel I checked another way (slightly altered version of one from MDN) ```js var triangle = {a:1, b:2, c:3}; function ColoredTriangle() { this.color = "red"; } ColoredTriangle.prototype = triangle; var...
I'm ok to agree if the value of the current implementation is higher. But if you associate a value into a class instance, does it preserve the prototype chain intact?...
the same issue. any progress here?
Hey @dosubot! The issue seems to be fixed as of [email protected]
@kabo the issue with combining all the types from different validators still persists