🐛 FIX: Make LONG-NAME optional in SpecRelationTypeParser#2
Open
🐛 FIX: Make LONG-NAME optional in SpecRelationTypeParser#2
Conversation
Per the ReqIF XSD, LONG-NAME is `use="optional"` for SPEC-RELATION-TYPE. The parser was treating it as required and crashing on spec-compliant files. Brings SpecRelationTypeParser in line with the other spec-type parsers (RelationGroupTypeParser, SpecObjectTypeParser, SpecificationTypeParser), which already handle missing LONG-NAME with a None fallback. Refs: useblocks/ubconnect#155
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.
Summary
SpecRelationTypeParserwas treatingLONG-NAMEas a required attribute andcrashing on spec-compliant ReqIF files that omit it. Per the ReqIF XSD,
LONG-NAMEisuse="optional"forSPEC-RELATION-TYPE— and every otherparser in this library already handles it as optional. This brings
SpecRelationTypeParserin line.Test plan
python -m pytest tests/unit/— 46 passed (3 new + 43 existing)Refs
Reported via useblocks/ubconnect#155