In the Extension Attributes example, the OData query we use should reference at least one extension attribute.
Open
Nobody has claimed this yet.
tech debt
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 6
Description
Right now the query just searches based on the name of the measurement. Since this example is about extension attributes, we should update the query to actually look for something related to extension attributes. Here's the query we're using in the LabVIEW and C# examples:
var oDataQuery = "$filter=testresult/hardwareitems/any (h: h/extension/cable_length eq '1.5') and Name eq 'scope reading'";
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the LabVIEW and C# examples containing the shown OData query and read the surrounding Extension Attributes example. Confirm that the query filters on an extension attribute, then update the example query where needed and verify both examples consistently demonstrate an extension-attribute lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100