pubsub: assure topic names are properly used in API requests #1008
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1005
Fixes #1006
Thanks to @chrishiestand for catching this bug.
We weren't considering that topic names come from two places:
projects/{id}/topics/{id}
){id}
)In either case, the
Topic
constructor comes up with their correct names in each format. But what it wasn't doing was passing the correct version (short format) toServiceObject
, which meant in some cases, the full format was being injected into a request URL where the short format was required.