Repository navigation
Conversation
Fixes the spelling of 'appropiate' to 'appropriate' in the docblock of Google\Http\MediaFileUpload::makePutRequest() in src/Http/MediaFileUpload.php. Documentation-only change. Refs googleapis#2729
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Fixes a spelling mistake in the docblock of
Google\Http\MediaFileUpload::makePutRequest().File:
src/Http/MediaFileUpload.php(line 160)/** * Sends a PUT-Request to google drive and parses the response, - * setting the appropiate variables from the response() + * setting the appropriate variables from the response()This is a documentation-only change — one word, no runtime behavior is affected.
Why
While reading
MediaFileUploadI noticed the wordappropiatein themakePutRequest()docblock. It is a user-visible typo in the PHP source that shows up in IDE hover tooltips and generated API docs, so it is worth a minimal one-word correction.Testing
No tests were added or changed: the patch touches only a comment. The existing test suite is unaffected by this change.
Related issue
Refs #2729