testkube-dashboard VS proposal-bind-operator

But createApi, as provided by RTK Query API, makes this quite a bit harder, or so it seems to me at least. How would you wrap createApi to provide such a functionality for every fetch by default?

[1]: https://github.com/kubeshop/testkube-dashboard

[2]: https://github.com/kubeshop/testkube-dashboard/tree/main/src...

There was also a different proposal that allows objects to be extended: https://github.com/tc39/proposal-bind-operator

Personally, I don't use classes much, but sometimes I think free functions a little bit hard to find, so I tend to experiment with the following pattern.

interface User { … }

const User = {

Yangi bind operatori Function.prototype.bind ni yanada elegant tarzda ishlatish imkonini beruvchi yangi sintaksis

In modern JS, you can export each function directly without putting them in an object. It also allows you to call a function with a specific “this” value, function.bind(object)(args). As a matter of fact, there’s a syntax proposal proposal and to do exactly this, object::function(args). This proposal could make what you describe pretty popular.

Hey, not yet ;)

This binding syntax (::)

You'd need 4 periods.

I don't think you want realms so much as protocols or extensions, the latter assimilating the beloved bind operator.