Repository navigation
docs: make callback.apiResponse argument a link to the upstream docs #1007
Description
continuing from #990 (comment)
Anywhere we document an apiResponse argument, we should be able to link it to the API docs that show what the user can expect from that object.
Tip: for most of the API docs I've seen, you can append a fragment #response to the URL to deep link to the relevant section.
Activity
callmehiphop commentedon Dec 8, 2015
Perhaps this would be better placed in gcloud-common?
stephenplusplus commentedon Dec 8, 2015
Possibly, but the task will be actually writing link tags in the JSDocs. Unless you can think of an automated way to do this with metadata from the big JSON doc?
callmehiphop commentedon Dec 8, 2015
Good point, it should probably just be in both.
stephenplusplus commentedon Nov 2, 2017
We are probably not going to make any changes to our GitHub hosted docs, as our repos start to migrate out onto cloud.google.com.
fix(deps): use google-gax v3.5.2 (#1007)
chore(deps): update dependency @types/mocha to v9 (#1007)
feat: add `gcf-owl-bot[bot]` to `ignoreAuthors` (#1007)
test: use fully qualified request type name in tests (#1007)
build: enable release-trigger bot (#1212) (#1007)
test: use fully qualified request type name in tests (#1007)
test: use fully qualified request type name in tests (#1007)
feat: Multi cluster routing (#1007)
feat: Multi cluster routing (#1007)
feat: Multi cluster routing (#1007)
feat: Multi cluster routing (googleapis#1007)