Add support for pydaq labels
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 9
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 1
Description
Expected Behavior
- labels are strings passed to
pydaq.Control.begin - we should be able to set this up ahead of time and pass them in to the various steps, or configure the next label without a transition
Current Behavior
- no support in the interface for this
Context
- Used for some of Dan Damiani's scripts
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 locating the interface around pydaq.Control.begin and the steps that would receive labels. Determine how labels can be configured before execution or changed for the next step without a transition, then verify that labels are passed through as strings to the relevant pydaq calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100