chore(API docs): Update docs to reflect sentry changes (#824)

Make docs reflect getsentry/sentry#12297, and a few other small changes which never got pulled in.

Author: lobsterkatie

__tests__/__snapshots__/documentation.js.snap

@@ -121,12 +121,12 @@ Array [
   "api/releases/delete-organization-release-file-details/index.html",
   "api/releases/delete-project-release-file-details/index.html",
   "api/releases/get-commit-file-change/index.html",
-  "api/releases/get-issues-resolved-in-release/index.html",
   "api/releases/get-organization-release-commits/index.html",
   "api/releases/get-organization-release-details/index.html",
   "api/releases/get-organization-release-file-details/index.html",
   "api/releases/get-organization-release-files/index.html",
   "api/releases/get-organization-releases/index.html",
+  "api/releases/get-project-issues-resolved-in-release/index.html",
   "api/releases/get-project-release-commits/index.html",
   "api/releases/get-project-release-file-details/index.html",
   "api/releases/get-project-release-files/index.html",

src/collections/_documentation/api/events/get-project-event-details.md

@@ -21,7 +21,7 @@
       "type": "string"
     }, 
     {
-      "description": "the hexadecimal ID of the event to retrieve (as reported by the raven client).", 
+      "description": "the id of the event to retrieve (either the numeric primary-key or the hexadecimal id as reported by the raven client)", 
       "name": "event_id", 
       "type": "string"
     }

src/collections/_documentation/api/events/put-project-group-index.md

@@ -14,6 +14,11 @@
       "name": "status", 
       "type": "string"
     }, 
+    {
+      "description": "additional details about the resolution. Valid values are `\"inRelease\"`, `\"inNextRelease\"`, `\"inCommit\"`,  `\"ignoreDuration\"`, `\"ignoreCount\"`, `\"ignoreWindow\"`, `\"ignoreUserCount\"`, and `\"ignoreUserWindow\"`.", 
+      "name": "statusDetails", 
+      "type": "map"
+    }, 
     {
       "description": "the number of minutes to ignore this issue.", 
       "name": "ignoreDuration", 

src/collections/_documentation/api/index.md

@@ -49,7 +49,7 @@ A full list of the currently supported API endpoints:
     -   [Create a New Release]({%- link _documentation/api/releases/post-organization-releases.md -%})
     -   [Update a Release]({%- link _documentation/api/releases/put-organization-release-details.md -%})
     -   [Delete a Release]({%- link _documentation/api/releases/delete-organization-release-details.md -%})
-    -   [List issues to be resolved in a particular release]({%- link _documentation/api/releases/get-issues-resolved-in-release.md -%})
+    -   [List issues to be resolved in a particular release]({%- link _documentation/api/releases/get-project-issues-resolved-in-release.md -%})
     -   Deploys
         -   [List a Release’s Deploys]({%- link _documentation/api/releases/get-release-deploys.md -%})
         -   [Create a Deploy]({%- link _documentation/api/releases/post-release-deploys.md -%})

src/collections/_documentation/api/organizations/get-organization-stats.md

@@ -33,7 +33,7 @@
       "type": "timestamp"
     }, 
     {
-      "description": "an explicit resolution to search for (eg: `10s`).  This should not be used unless you are familiar with Sentry's internals as it's restricted to pre-defined values.", 
+      "description": "an explicit resolution to search for (one of `10s`, `1h`, and `1d`)", 
       "name": "resolution", 
       "type": "string"
     }

src/collections/_documentation/api/projects/get-project-stats.md

@@ -38,7 +38,7 @@
       "type": "timestamp"
     }, 
     {
-      "description": "an explicit resolution to search for (eg: `10s`).  This should not be used unless you are familiar with Sentry's internals as it's restricted to pre-defined values.", 
+      "description": "an explicit resolution to search for (one of `10s`, `1h`, and `1d`)", 
       "name": "resolution", 
       "type": "string"
     }

src/collections/_documentation/api/releases/get-issues-resolved-in-release.md renamed to src/collections/_documentation/api/releases/get-project-issues-resolved-in-release.md

@@ -20,7 +20,7 @@ title: Releases
 - [Create a Deploy]({%- link _documentation/api/releases/post-release-deploys.md -%})
 - [List an Organization Release's Commits]({%- link _documentation/api/releases/get-organization-release-commits.md -%})
 - [List a Project Release's Commits]({%- link _documentation/api/releases/get-project-release-commits.md -%})
-- [List issues to be resolved in a particular release]({%- link _documentation/api/releases/get-issues-resolved-in-release.md -%})
+- [List issues to be resolved in a particular release]({%- link _documentation/api/releases/get-project-issues-resolved-in-release.md -%})
 - [List a Project Release's Files]({%- link _documentation/api/releases/get-project-release-files.md -%})
 - [Upload a New Project Release File]({%- link _documentation/api/releases/post-project-release-files.md -%})
 - [Retrieve a Project Release's File]({%- link _documentation/api/releases/get-project-release-file-details.md -%})

src/collections/_documentation/api/releases/index.md

@@ -40,7 +40,7 @@
       "type": "array"
     }, 
     {
-      "description": "an optional way to indicate the start and end commits for each repository included in a release. Head commits must include parameters `repository` and `commit` (the HEAD sha). They can optionally include `previousCommit` (the sha of the HEAD of the previous release), which should be specified if this is the first time you've sent commit data.", 
+      "description": "an optional way to indicate the start and end commits for each repository included in a release. Head commits must include parameters `repository` and `commit` (the HEAD sha). They can optionally include `previousCommit` (the sha of the HEAD of the previous release), which should be specified if this is the first time you've sent commit data. `commit` may contain a range in the form of `previousCommit..commit`", 
       "name": "refs", 
       "type": "array"
     }

src/collections/_documentation/api/releases/post-organization-releases.md

@@ -38,7 +38,7 @@
       "type": "timestamp"
     }, 
     {
-      "description": "an explicit resolution to search for (eg: `10s`).  This should not be used unless you are familiar with Sentry's internals as it's restricted to pre-defined values.", 
+      "description": "an explicit resolution to search for (one of `10s`, `1h`, and `1d`)", 
       "name": "resolution", 
       "type": "string"
     }