feat: add http adapter support for glee

[ritik307]

Description

Implement the HTTP adapter for both server and client

Aims to -

• connect HTTP server as per the specification.
• Handle incoming messages only on the channels specified in the specification
• Send appropriate responses from the registered function.
• connect the HTTP client as per the specification.
• HTTP client should be able to connect via any other protocol and provide response in the specified registered function.

Steps to test the codeflow

Steps to run the base code

1. npm i
2. npm run dev

Steps to run the server
4. cd examples/anime-http/server
5. npm i
6. npm run dev

Steps to run the client
8. cd examples/anime-http/client
9. npm i
10. npm run dev

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[fmvilas]

Left a few comments.

Along with those, I'm adding two more generic comments here:

1. What does "adding HTTP header init" means? 😄
2. It would be great if you can consider making it clear when it should be creating an HTTP server and when it should be creating a client (client can be done in another PR). For instance, if the server is marked as "local", then it should create a server. Otherwise, it shouldn't. See an example here: https://github.com/asyncapi/glee/pull/319/files#diff-5a59976f2bbdbefa8fb1b10842622e9c61def3c47869b93b2d0d3d1374530734R21.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

No Coverage information
0.0% Duplication

[ritik307]

Left a few comments.

Along with those, I'm adding two more generic comments here:

1. What does "adding HTTP header init" means? smile
2. It would be great if you can consider making it clear when it should be creating an HTTP server and when it should be creating a client (client can be done in another PR). For instance, if the server is marked as "local", then it should create a server. Otherwise, it shouldn't. See an example here: https://github.com/asyncapi/glee/pull/319/files#diff-5a59976f2bbdbefa8fb1b10842622e9c61def3c47869b93b2d0d3d1374530734R21.

Sorry for that I will try to be more clear on the commit messages 🙂

[ritik307]

@fmvilas Can you kindly provide me with some resources to study web sockets, I am baffled with web sockets at the moment.😟

[fmvilas]

Sure, MDN has a great resource: https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API.

[Souvikns]

Since you are adding a new adapter to support the HTTP server you have to update the docs accordingly.

[ritik307]

@Souvikns I have changed the examples/simple/asyncapi.yaml file according to the docs that you have referred but i am not sure whether i used $ref: '#/components/messages/testReply' at correct place or not. Kindly check it and let me know if any further changes are required

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

No Coverage information
0.0% Duplication

[KhudaDad414]

LGTM!

[fmvilas]

Left some comments

[ritik307]

@fmvilas Made the changes you have suggested. Please check

[fmvilas]

Left some more comments. Please don't rush it out. Take your time to evaluate what's the best solution. For instance, I see you're repeating { [key: string]: string } | { [key: string]: string[] } in multiple places. Maybe it's time to define it as a custom type to reuse it.

[fmvilas]

Left a few more suggestions

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[fmvilas]

LGTM 👍

[Souvikns]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.20.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀