Open
Conversation
Member
|
This repo isn't under active development and I'm unlikely to get around to reviving it any time soon. Ultimately the hard-coded parsing approach isn't the correct way to handle STEP files because they're defined by other schema files and I just haven't had the time to fully investigate that approach. I've started that method in the |
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.
I've been working on an app to convert STEP to SVG for laser cutting. From time to time, I've bumped into sample step files that couldn't be parsed with your library. I'm using Claude Opus to help me with the hard parts that are over my head. This is what it created to get past my problems. Please feel free to accept this or cherry pick from it if you find it useful. For the latest change, I had it add an md file explaining why the changes were needed.