-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "contact" information to definition #10
Comments
Many sense will add. |
* Create 0.1.0.yml Initial commit of SQS extension supporting both FIFO & Standard queues. * Update 0.1.0.yml Updated Examples and typo change for SQS Initial commit * Update extensions/sqs/0.1.0.yml Correction of type. Co-Authored-By: Fran Méndez <fmvilas@gmail.com> * Update 0.1.0.yml Add Contact block. #10 Add Tags to help search/filtering. #9 Co-authored-by: Fran Méndez <fmvilas@gmail.com>
This issue has been automatically marked as stale because it has not had recent activity 😴 |
closing for now catalog is super simplified now, as binding, any other improvements can be pushed but when there is really a dedicated person that can work on it, own discussion and lead till the end |
Reason/Context
Knowing who to contact when using an extension might be difficult with no other information than the name of the author.
Description
It would be great to add a "contact" field with more information on who to contact for questions, bugs, or feature requests. The "contact" object can have the same information as the AsyncAPI one.
Example
The text was updated successfully, but these errors were encountered: