microsoft / microsoft/fhir-server
Optimize ExecuteAsync calls
Open
Nobody has claimed this yet.
Up for grabs
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
**User story**
As described in [this PR comment](https://github.com/microsoft/healthcare-shared-components/pull/197#discussion_r603707137), some calls to ExecuteAsync can be optimized to accept cancellation tokens directly.
**Acceptance criteria**
ExcuteAsync calls are optimized.
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 linked discussion in PR 197, then locate the ExecuteAsync call sites in the repository and compare how cancellation tokens are passed. Done means the applicable calls accept cancellation tokens directly and the existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100