functions that accept neither cbdate or cedate parameters
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 26
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
There are quite a few API calls that accept neither the cbdate nor the cedate parameters. The only functions that should accept these parameters are:
API calls that use the "Sample Data" service
API calls that use the "dailyData" service
API calls that use the "quarterlyData" service
API calls that use the "annualData" service
API calls that use the "transactionsSample" service
Any other exported RAQSAPI function should not be accepting either the cbdate or cedate parameters.
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 inventorying the exported RAQSAPI functions and identifying which ones use the five listed services. Compare their parameter signatures with the cbdate and cedate rule; done means only those service calls accept either parameter and the other exported functions do not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100