Link about EONET API documentation leads to depracated API.
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
"Please see our API documentation to learn more about how to use the EONET web services."
Should link to "Please see our API documentation to learn more about how to use the EONET web services." so people know there's an updated version of the API.
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
Search the documentation for the sentence linking to EONET API documentation and inspect the surrounding page or source file. Update the link from http://eonet.gsfc.nasa.gov/docs/v2.1 to https://eonet.gsfc.nasa.gov/docs/v3, then verify the rendered documentation points to the current API version.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100