Repository navigation
fix(ids): check a type object's own property sets in IDSProperty - #824
Merged
Merged
Conversation
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.
Description
Fixes #823.
IDSProperty.getTypePsetsnow also returns the item's ownHasPropertySets. So when the applicability selects a type object (e.g.IFCWALLTYPE), its own property sets are checked. Before, only the sets of the item's type definitions were read, which covers occurrences inheriting from their type but not the type itself.Additional context
facets/property-type-object.test.tsontests/fixtures/type-psets.ifc:IFCWALLTYPE+Pset_WallCommon.IsExternal = TRUEpasses forIfcWallTypeTest feature #52. It fails without the change. The buildingSMART IDS test caseproperty/pass-properties_can_be_inherited_from_the_type_2_2(applicabilityIFCWALLTYPE) also fails onmainand passes with it.vitest --runinpackages/core: all pass, with no change to existing tests.tsc -p tsconfig-build.json --noEmitis clean.property.test.ts.What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following:
feat(examples): add hello-world example).fixes #123).