Repository navigation
list what arguments go into the callback #628
Copy link
Copy link
Closed
Labels
type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Description
Activity
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
on May 26, 2015 Yeah, I think that'd be great to document 👍
- changed the title
[-]gcloud.storage.createBucket documentation doesn't say what arguments go into the callback[/-][+]list what arguments go into the callback[/+]on Jun 17, 2015 - added a commit that references this issue
on Sep 27, 2022 12 remaining items
- added a commit that references this issue
on Jan 28, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 23, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 17, 2026 - added a commit that references this issue
on Mar 18, 2026
Metadata
Metadata
Assignees
Labels
type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
I think this is actually a more widely spread problem, where the examples have been saving us, but...
Is there any way we could more broadly document the arguments that go into the callback function?