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

CSS2DObject and CSS3DObject: Remove broken generics and make renderer parameter unknown #18520

Merged
merged 1 commit into from
Jan 31, 2020

Conversation

juliendargelos
Copy link
Contributor

@juliendargelos juliendargelos changed the title CSS2D and CSS3D renderers: Remove broken generics and make renderer parameter unknown CSS2DObject and CSS3DObject: Remove broken generics and make renderer parameter unknown Jan 30, 2020
@mrdoob mrdoob added this to the r113 milestone Jan 31, 2020
@mrdoob mrdoob merged commit 4b186eb into mrdoob:dev Jan 31, 2020
@mrdoob
Copy link
Owner

mrdoob commented Jan 31, 2020

Thanks!

@mrdoob
Copy link
Owner

mrdoob commented Jan 31, 2020

Does this deserve pushing the npm package to 0.113.2?

@juliendargelos
Copy link
Contributor Author

This was quite a nonsense and will cause type errors on existing typescript code that uses render callbacks:

onBeforeRender: <Renderer = WebGLRenderer>(
renderer: Renderer,

So I think the fix should be pushed

@mrdoob
Copy link
Owner

mrdoob commented Jan 31, 2020

Done!

@Mugen87
Copy link
Collaborator

Mugen87 commented Jan 31, 2020

Well, that's why I'm not a fan of static typing^^.

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.

3 participants