buildingSMART / buildingSMART/IDS
Multiple matched Attributes
- Dominant language
- C#
- Stars
- 318
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
From facet-configurations:
NAME: The Attribute should be populated (i.e. not null) (this is different from the Property facets, which accepts a null)
NAME/VALUE: all matching attributes must match the value constraints (excludes null)
Look at test pass-name_restrictions_will_match_any_result_2_3.
It passed. So, looks like for multiple attributes text above should be 'NAME: **The ANY OF** Attribute**S** should be populated (i.e. not null)'
Is it wrong test? If not, why NAME/VALUE case use 'ALL' word and different from NAME case.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the pass-name_restrictions_will_match_any_result_2_3 test and the facet-configurations rules quoted in the issue. Compare the NAME and NAME/VALUE matching behavior and wording; done means the test, implementation behavior, and documented constraint agree on whether matching is ANY or ALL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100