EOSPAC option setting
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
What are the implications of setting options before an eospac call? Especially for scalar calls? We should discuss with the EOSPAC folks to find out if this is a reasonable way of using eospac.
If it is not reasonable, we should redesign the eospac class to avoid having to set options in this way.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by locating the EOSPAC option-setting and scalar-call paths, then consult the EOSPAC folks about whether setting options before a call is supported and reasonable. Done means the usage is validated or the required redesign of the EOSPAC class is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100