You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the proposal have any plans for extending existing operators? In our internal implementation, we modify operators using imports of modules that modify the prototype. We think it'd be better if there was an API like customElements.define (e.g. observables.define) that would allow extending the operator API.
The text was updated successfully, but these errors were encountered:
we modify operators using imports of modules that modify the prototype. We think it'd be better if there was an API like customElements.define (e.g. observables.define) that would allow extending the operator API.
Can you describe why your proposed method of extensibility would be desirable? What does it provide over your current solution?
You can define additional requirements with the indirection. For example, the operator is required to be a function.
We have had success in just using the prototype, so I wouldn't say the proposed solution is necessary. This question is more about guidance/expectation.
Does the proposal have any plans for extending existing operators? In our internal implementation, we modify operators using imports of modules that modify the prototype. We think it'd be better if there was an API like customElements.define (e.g. observables.define) that would allow extending the operator API.
The text was updated successfully, but these errors were encountered: