Fix STEP import unit guidance - #1032
Merged
Merged
Conversation
JordanNoone
requested review from
Irev-Dev,
adamchalmers,
franknoirot and
jessfraz
as code owners
September 9, 2026 03:10
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
1 participant
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.
Summary
Why
The deployed import overview contradicts the maintained STEP-specific page and current Modeling App behavior. A 50 mm STEP part imported into an inch scene can measure 50 in, so the incorrect overview claim can produce a 25.4x scale error.
Closes #1031.
Related work
PR #991 includes the same unit correction inside a broader imported-geometry rewrite, but it currently conflicts with
main. This PR isolates the deployed unit-guidance defect in one owned documentation file so it can be reviewed and merged independently.Validation
npm cinpm run build— generated 714 documentsgit diff --check