File extensions does not have to be .alert .dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 32/100
Research direction
Start by tracing how the pull and push commands determine resource file extensions; the issue does not name specific files or tests. Confirm that alert and dashboard resources can consistently use .json, and verify that both commands still read and write the same extension when the resource type is supplied.
Written by the indexing model from the issue text.
Description
We are talking about the files where wavectl stores the json representation of resources. ( Alerts or Dashboards)
The file syntax is actually .json.
So for IDE support aspect, it makes sense to use the extension json.
The wavectl command could read the expected extension in an environment variable. But, I am actually not sure whether this is necessary. I do not think there is anything fundamental in the implementation that would break if we changed the .alert extension to .json.
In wavectl commands the user needs to specify the resource type already. For example
wavectl pull
wavectl push dashboard
So as long as the pull and the push command's file extension expectations are the same, using .json should work simply.
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
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.
More from box/wavectl
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Add coverage tests Opentestplan
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
testplan
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·