-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Bump Three.js to r84 #2456
Bump Three.js to r84 #2456
Conversation
… THREE.GLTFLoader specification
src/core/a-assets.js
Outdated
because of THREE.GLTFLoader specification. | ||
*/ | ||
if (!responseType) { | ||
var extension = ''; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd make this code a private exported function inferResponseType (src)
and test on its own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comment.
What does 'test on its own' mean in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can test the function by calling it directly rather than creating a-asset-item
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's very useful. I will update.
Updated. |
Description:
This PR bumps Three.js to r84.
Because of
THREE.GLTFLoader
specification in r84 or newer,.gltf
and.glb
files need to be loaded asarraybuffer
.I let
a-asset-item
automatically setarraubuffer
response-type attribute for them.I think this automation is necessary because of
FYI,
THREE.GLTFLoader
in r84Changes proposed:
a-asset-item
detects glTF files from their extensions and automatically setsarraybuffer
response-type attribute.