Skip to content

Some component reference docs show optional destructive parameters in the example #1605

@AaronCrawfis

Description

@AaronCrawfis

Describe the issue
Some component specs show optional parameters that might cause messages to timeout, be deleted, or do other things are are not expected for users looking to get started with that component.

Expected content
All components should have a copy and paste experience that makes it easy to get up and running quickly, with additional docs on how to add optional behavior.

Additional context
Azure Service Bus had docs that had users copy and paste code that would lead to messages timing out and being deleted, making it hard to know why messages weren't being delivered. See #1604 for context

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions