Change shore hardness name and category to be consistent with openprinttag-architecture - #148
Merged
Merged
Conversation
Done for consistency with openprinttag-database
Collaborator
|
Please add rationale to the comment/pr description - that we're fixing a mismatch with OPT-arch |
CZDanol
approved these changes
Aug 25, 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
2 participants
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.
The specification declares FFF-specific fields
shore_hardness_aandshore_hardness_d. This is inconsistent withopenprinttag-architecture, which instead specifieshardness_shore_aandhardness_shore_dfor both material types. I suggest fixing this inconsistency here by removing thecategoryfrom both fields and renaming them, while keeping the same key.