Fix import path of WebAPIResource in extension documentation.
Review Request #10319 — Created Nov. 11, 2018 and submitted
We had a bad import path in the sample code for implementing a new
API resource in an extension. This change fixes it.
This is also incorrect. "Request" -> "request", but more importantly, it should be:
from reviewboard.webapi.resources import resources ... resources.review_request
In fact, the original import (
WebAPIResource) from this module was actually valid.
.baseis what the other resources use in order to avoid circular import issues, and no doubt we'll support both going forward, but probably we'd want to standardize on importing this from