Write a doc for NATS connector and inbound endpoint
Open
Nobody has claimed this yet.
API-M-4.0.0
API-M-4.1.0
API-M-Master
Severity/Minor
Type/Improvement
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
- Write a scenario document for NATS connector. Reference [1]
- Write a document for inbound endpoint. Please follow the structure of an existing inbound EP as [2].
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the file-connector scenario documents in the linked ConnectorTest directory and the linked JMS inbound endpoint properties page. Use their structure and coverage as references, then document the NATS connector scenario and the inbound endpoint. Done means both documents are added with the requested reference-based structure and content.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100