Closed echadwick-artist closed 2 years ago
Hi @echadwick-wayfair, adding this autocomplete list to the extensionsUsed
field is not easily done, for technical reasons (extensionsUsed
is a JSON array of strings, where extensions
is a JSON object with known properties, so the JSON schemas are quite different).
But there is a new "Quick Fix", added last November in #227, that can help you out here. Once you've added that KHR_materials_iridescence
to the extensions
block, you'll see this:
The red squiggle is glTF Validator complaining I didn't mark the extension as used yet. But notice I've put my cursor on the name of the extension, and there's a blue light-bulb in the left margin. This is the "Quick Fix" indicator.
The same "Quick Fix" is also offered in a popup if you hover it:
Clicking either of these will offer the only Quick Fix this project has to offer so far:
Clicking that option will edit your document, possibly in a place far from your cursor, to add or update the extensionsUsed
section. You may not immediately see what it did, but you should immediately see the red squiggle disappear, as the glTF Validator no longer has that particular concern about your document.
Oooh nice! This is great, thank you!
It would be helpful to add autocomplete for extensionsUsed.
Currently, autocomplete is great for adding extensions within a material. But it seems to be missing when adding extenstions to extensionsUsed.
"ext
and autocomplete suggests a few optionsextensionsUsed
suggestion"