Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split IObservableFactories type definition and implementation #1257

Merged
merged 1 commit into from
Dec 4, 2017
Merged

Split IObservableFactories type definition and implementation #1257

merged 1 commit into from
Dec 4, 2017

Conversation

Obi-Dann
Copy link
Contributor

@Obi-Dann Obi-Dann commented Nov 26, 2017

It seems the only reason to keep IObservableFactories as a class is to avoid declaring type definition and implementation separately. However, it does not seem to be entirely correct approach at runtime, because it's never expected that a new instance of IObservableFactories will be created. In addition, reading properties of prototype cause issues with some browsers.

Issue #1238

It seems the only reason to keep IObservableFactories as a class is to avoid declaring type definition and implementation separately. However, it does not seem to be entirely correct approach at runtime, because it's never expected that a new instance of IObservableFactories will be created. In addition, reading properties of prototype cause issues with some browsers.
@mweststrate
Copy link
Member

Merged, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants