Investigate the need for defining constants in nimi-python API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
Description of issue
In driver C APIs, there usually are constants defined to represent certain magic numbers. e.g. In nidigital, there is NIDIGITAL_VAL_ACQUIRE_ALL_SAMPLES (= -1), intended to represent capturing all available History RAM samples in FetchHRAMData() function.
There isn't a way to represent these magic number in nimi-python API. We should consider adding something similar.
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
Start by reviewing the nimi-python driver APIs, especially nidigital's FetchHRAMData() and the corresponding C API constant NIDIGITAL_VAL_ACQUIRE_ALL_SAMPLES. The issue names no files or tests; done requires deciding whether magic-number constants are needed and defining the scope of any API change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100