Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: upstream links #790

Merged
merged 1 commit into from
Aug 14, 2015
Merged

docs: upstream links #790

merged 1 commit into from
Aug 14, 2015

Conversation

callmehiphop
Copy link
Contributor

Closes #740

Added links for all upstream counterparts.

demo

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Aug 10, 2015
@@ -56,6 +56,9 @@ function Dataset(bigQuery, id) {
/**
* Create a table given a tableId or configuration object.
*
* See [Tables: insert](https://cloud.google.com/bigquery/docs/reference/v2/tables/insert)

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@callmehiphop
Copy link
Contributor Author

@stephenplusplus so I kinda think the overall appearance of the links could be better, what are your feelings on doing something like this..

/**
 * <div class="notice">See [Tables: insert](https://cloud.google.com/bigquery/docs/reference/v2/tables/insert)
 * for more detailed information.</div>
 */

@stephenplusplus
Copy link
Contributor

Could you post a screenshot of what that renders like?

@callmehiphop
Copy link
Contributor Author

Initially I tried use blockquote markdown syntax (which works) but there isn't any styling associated with it. Alternatively I could write some CSS for that and we could go that route.

@stephenplusplus
Copy link
Contributor

That looks cool to me. Semantics: would just a manual a tag be better?

@callmehiphop
Copy link
Contributor Author

That looks cool to me. Semantics: would just a manual a tag be better?

Instead of the markdown link syntax? [text](http://link.com)?

@stephenplusplus
Copy link
Contributor

Yeah, I'm thinking since we have to add a class, we don't need the extra
div wrapper if we just write out the a.

On Monday, August 10, 2015, Dave Gramlich notifications@github.com wrote:

That looks cool to me. Semantics: would just a manual a tag be better?

Instead of the markdown link syntax? text?


Reply to this email directly or view it on GitHub
#790 (comment)
.

@callmehiphop
Copy link
Contributor Author

Well, if I understand correctly, that's going to turn the entire sentence into a link? I'm probably splitting hairs, but I think that would be kind of ugly. We could just write some styles to make the blockquote look the same as the notice class and go full out markdown.

@stephenplusplus
Copy link
Contributor

Nope you're right. I'm just getting myself confused. Sorry!

For the text, wdyt about just "Official API documentation"

And if it's just the one line, we can use the a tag with a class, unless you think that's a bad idea.

Official API documentation.

@stephenplusplus
Copy link
Contributor

It looks awesome! Moving the link to a jsdoc property makes it much easier to make changes now without having to go through all of the docs.

I would prefer the links move to the top, as we want to get across "see the API docs for more information about our parameters". Here's an example:

screen shot 2015-08-10 at 8 40 15 pm

Can you think of another way to make it clear that the official docs have more information on the properties we accept?

Also note, I changed "Code on GitHub" to "Source Code". Small change, but "Code on GitHub" just reads like a bad sentence to me. "Source Code" is direct and concise!

@callmehiphop
Copy link
Contributor Author

I would prefer the links move to the top, as we want to get across "see the API docs for more information about our parameters".

Done!

Can you think of another way to make it clear that the official docs have more information on the properties we accept?

I think maybe just make a note within the object description? e.g. - Configuration object. For a complete list of properties please refer to the Official API Documentation.

It's also possible to give each resource link a custom title from JSDoc, so we could alter the link title to convey this as well. Perhaps instead of Official API Documentation you could say Complete List of Configuration Options or something..

Also note, I changed "Code on GitHub" to "Source Code". Small change, but "Code on GitHub" just reads like a bad sentence to me. "Source Code" is direct and concise!

I can dig it.

@stephenplusplus
Copy link
Contributor

LGTM.

@jgeewax wdyt? Did we make things better or regress?

@callmehiphop callmehiphop changed the title Upstream links docs: upstream links Aug 12, 2015
@stephenplusplus stephenplusplus mentioned this pull request Aug 12, 2015
18 tasks
@jgeewax
Copy link
Contributor

jgeewax commented Aug 12, 2015

So it's definitely a step forward, however... I have to say I liked the "See: Tables.insert [ -> ] for more information" since it ties it to the specific method (aka, I know I'm not being dumped off to some marketing landing page somewhere that's ridiculous...)

Is it too much work to do that? (Fully understand if so.)

Ideally, text might be something like...

"See: Tables.insert [ -> ] API method for more information"

@callmehiphop
Copy link
Contributor Author

Is it too much work to do that?

It definitely isn't!

@stephenplusplus thought it would be nice to move the source code link into the same block and while doing that I also found links for concepts/references/etc. scattered across the api so I decided to consolidate them all. (e.g. http://callmehiphop.github.io/gcloud-node/#/docs/master/storage/bucket?method=acl)

Is that something you like and would want to keep? If so, I think maybe the verbiage "See: Tables.insert for more information" might sound kinda funny in a list of links opposed to something like "Tables.insert REST API Documentation"

Thoughts?

@jgeewax
Copy link
Contributor

jgeewax commented Aug 12, 2015

Gotcha

Phrased as a list of links, definitely "Tables.insert API documentation (official)" or similar makes sense

Is it crazy to move the resources down as well? Logically they make sense above, but when I'm looking at docs, examples are likely going to be ... far more important than the link to the API docs...

Maybe call it "More information" and put it at the bottom?

@callmehiphop
Copy link
Contributor Author

Personally I think it makes sense - a user is probably only going to want to see the full documentation if the examples don't provide them with the information they need. So having the links below the examples is probably more convenient.

However, I think the whole reason @stephenplusplus opened an issue about this is because we don't document all the available options that a user can pass in for some methods. Having the links right above the options as well as a comment in the options description telling the user to visit the official API documentation kinda solved that.

@stephenplusplus
Copy link
Contributor

How about this or something similar?

screen shot 2015-08-12 at 9 28 11 pm

@callmehiphop
Copy link
Contributor Author

Updated the link titles & placement and pushed, let me know what you guys think!

updated lint rules to ignore 80+ chars for comment urls

created resource section

added more descriptive link titles and moved resources to the bottom

changed @apidocs to @resource
@stephenplusplus
Copy link
Contributor

Awesome. Just. Awesome.

stephenplusplus added a commit that referenced this pull request Aug 14, 2015
@stephenplusplus stephenplusplus merged commit 173c5f9 into googleapis:master Aug 14, 2015
@callmehiphop
Copy link
Contributor Author

💃

@callmehiphop callmehiphop deleted the upstream-links branch August 14, 2015 02:34
sofisl pushed a commit that referenced this pull request Nov 10, 2022
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@google-cloud/storage](https://togithub.com/googleapis/nodejs-storage) | [`^5.0.0` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@google-cloud%2fstorage/5.20.5/6.1.0) | [![age](https://badges.renovateapi.com/packages/npm/@google-cloud%2fstorage/6.1.0/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/@google-cloud%2fstorage/6.1.0/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/@google-cloud%2fstorage/6.1.0/compatibility-slim/5.20.5)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/@google-cloud%2fstorage/6.1.0/confidence-slim/5.20.5)](https://docs.renovatebot.com/merge-confidence/) |

---

### Configuration

📅 **Schedule**: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. ⚠ **Warning**: custom changes will be lost.

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/nodejs-translate).
sofisl pushed a commit that referenced this pull request Nov 11, 2022
[![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [sinon](https://sinonjs.org/) ([source](https://togithub.com/sinonjs/sinon)) | [`^9.0.2` -> `^10.0.0`](https://renovatebot.com/diffs/npm/sinon/9.2.4/10.0.0) | [![age](https://badges.renovateapi.com/packages/npm/sinon/10.0.0/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/sinon/10.0.0/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/sinon/10.0.0/compatibility-slim/9.2.4)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/sinon/10.0.0/confidence-slim/9.2.4)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>sinonjs/sinon</summary>

### [`v10.0.0`](https://togithub.com/sinonjs/sinon/blob/master/CHANGELOG.md#&#8203;1000--2021-03-22)

[Compare Source](https://togithub.com/sinonjs/sinon/compare/v9.2.4...v10.0.0)

==================

-   Upgrade nise to 4.1.0
-   Use [@&#8203;sinonjs/eslint-config](https://togithub.com/sinonjs/eslint-config)[@&#8203;4](https://togithub.com/4) => Adopts ES2017 => Drops support for IE 11, Legacy Edge and legacy Safari

</details>

---

### Renovate configuration

:date: **Schedule**: "after 9am and before 3pm" (UTC).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

:no_bell: **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/nodejs-dialogflow).
sofisl pushed a commit that referenced this pull request Jan 24, 2023
sofisl pushed a commit that referenced this pull request Jan 24, 2023
sofisl pushed a commit that referenced this pull request Jan 25, 2023
sofisl pushed a commit that referenced this pull request Jan 25, 2023
sofisl added a commit that referenced this pull request Sep 13, 2023
* docs: fix node release schedule link

Co-authored-by: Jeffrey Rennie <rennie@google.com>

Source-Link: googleapis/synthtool@1a24315
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:e08f9a3757808cdaf7a377e962308c65c4d7eff12db206d4fae702dd50d43430

* chore!: upgrade to Node 14

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Sofia Leon <sofialeon@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants