fix: custom body plans not imported correctly#2784
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes incorrect handling of custom (non-dictionary) GCS body plans during import so that removed hit locations don’t get reintroduced and custom roll ranges (e.g., expanded Torso range) are preserved.
Changes:
- Preserve GCS-provided
calc.roll_rangeon imported hit locations when it’s not the default placeholder. - Avoid auto-creating “missing” default hit locations when the body plan table was not found by exact name (i.e., when the table was inferred/guessed).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mjeffw
approved these changes
Jul 15, 2026
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 #1832