recognize .wrl as a vrml export extension#2073
Open
tylergibbs1 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #740
.wrlis the extension most vrml tools recognize, but cadquery only inferredVRMLfrom.vrml. this maps.wrlto the existing vrml exporter for both shapes and assemblies.the exporter test now verifies that
.vrmland.wrlproduce the same vrml header. the assembly save and export cases also infer the format from.wrlinstead of passing it explicitly.validation
full pytest was not run locally because this checkout does not have the occt runtime installed.