Fix deprecation warnings
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- backend
Research direction
Start by inspecting the listed locations in src/DataSource.ts, src/common/annotationsFromDataFrame.ts, src/module.ts, and src/types.ts. Read the linked RxJS deprecation guidance and the replacement APIs referenced in the warnings, then run the repository's existing checks to confirm the listed deprecation warnings are gone.
Written by the indexing model from the issue text.
Description
-
src/DataSource.ts
- deprecation/deprecation: 'toPromise' is deprecated. Replaced with {@link firstValueFrom } and {@link lastValueFrom }. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise at line 67, column 41
- deprecation/deprecation: 'toPromise' is deprecated. Replaced with {@link firstValueFrom } and {@link lastValueFrom }. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise at line 96, column 45
- deprecation/deprecation: 'toPromise' is deprecated. Replaced with {@link firstValueFrom } and {@link lastValueFrom }. Will be removed in v8. Details: https://rxjs.dev/deprecations/to-promise at line 116, column 45
-
src/common/annotationsFromDataFrame.ts
- deprecation/deprecation: 'get' is deprecated. Use [idx]. This only exists to help migrate Vector to Array at line 120, column 30
-
src/module.ts
- deprecation/deprecation: 'setVariableQueryEditor' is deprecated. -- prefer using {@link StandardVariableSupport} or {@link CustomVariableSupport} or {@link DataSourceVariableSupport} in data source instead at line 15, column 4
-
src/types.ts
- deprecation/deprecation: 'DataQuery' is deprecated. use the type from at line 136, column 49
- Dominant language
- Go
- Stars
- 311
- Forks
- 72
- Avg merge
- 7d 10h
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from grafana/github-datasource
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
grafana/github-datasource#796 · 2 comments ·
-
Bug: Workflow_Runs query type consistently returns 0 rows when same URL+token directly returns dataOpen
Difficulty 4/5 3-5 days Newbie friendliness 52/100
grafana/github-datasource#774 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
grafana/github-datasource#760 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
grafana/github-datasource#528 · 4 comments ·
-
Dependency DashboardOpen
Difficulty 4/5 3-5 days Newbie friendliness 12/100
grafana/github-datasource#523 ·
All issues in grafana/github-datasource
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
pion/interceptor#479 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yetone/magpie#1035 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
slavakurilyak/awesome-ai-agents#710 ·
Maintainers usually reply within 1 day
-
`renderLinkedIssues` overshoots its byte budget: unresolved and omitted lists are never boundedOpenagent-butler-finding agent-research-recommend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4614 · 1 comment ·
Maintainers usually reply within 1 day