Add Video Intelligence v1beta2 GAPIC#1702
Conversation
|
@blowmage After this is merged, could you create a point release? |
|
@geigerj Do you want |
|
Ah, right... I'll update the Rakefile. |
|
We will need to update the dependency on |
I'm not sure what you mean by "point release". The current release is |
|
I can follow this PR up with another PR making the additional changes needed. |
|
Updated Rakefile and gemspec. Re: versions, please follow whatever convention you've been following. For GAX, we've used a minor release increment to indicate a breaking change when in major version 0, but it's fine to use it here if that's what you've been doing for large changes like a new API version. |
|
|
||
| gem.add_dependency "google-gax", "~> 0.8.0" | ||
| gem.add_dependency "google-gax", "~> 0.8.6" | ||
| gem.add_dependency "googleapis-common-protos", "~> 1.3.1" |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Ignore the main required file as it violates many rules.
In order to docucment method arguments that aren't declared you must use the @overload tag.
This will resolve the warning: Error loading plugin 'yard-doctest'
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
I am the author of these commits. |
|
@quartzmo I had to massage the YARD formatting to get these changes to pass the CI build, as well as to add the new classes to the documentation output. Can you look them over and give some feedback? Is this the right approach? |
|
@blowmage Thank you for the fixes. Once we're set on the right YARD formatting, I'll get fixes in to the generator. |
|
@blowmage Your YARD fixes look good to me! |
Based on feedback from googleapis/google-cloud-ruby#1702
Based on feedback from googleapis/google-cloud-ruby#1702
Based on feedback from googleapis/google-cloud-ruby#1702
Based on feedback from googleapis/google-cloud-ruby#1702 - Use "@overload" to prevent YARD from being confused when @param docs do not match the *args, **kwargs method signature - Do not use *args, **kwargs when the true method signature is known - End version index files in newline, per convention
Based on feedback from googleapis/google-cloud-ruby#1702 - Use "@overload" to prevent YARD from being confused when @param docs do not match the *args, **kwargs method signature - Do not use *args, **kwargs when the true method signature is known - End version index files in newline, per convention
No description provided.