influxdata / influxdata/docs-v2
Add use case and value statements for each dashboard variable type
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Each dashboard variable type has a specific purpose and value proposition. We should include these in the descriptions of each variable type.
- [ ] Map – Maps a string value to another. Essentially lets you create human readable aliases for other values.
- [ ] Query – Dynamically populates the variable value options.
- [ ] CSV - Static populates the variable value options.
##### Relevant URLs
- https://docs.influxdata.com/influxdb/cloud/visualize-data/variables/variable-types/
- https://docs.influxdata.com/influxdb/2.4/visualize-data/variables/variable-types/
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
Start with the variable types documentation at the linked Cloud or InfluxDB 2.4 URL and review the Map, Query, and CSV sections. Done means each type's description includes its specific use case and value statement, with all three checklist items addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100