support address parameters in channels

[KhudaDad414]

Reason/Context

suppose I have the following AsyncAPI spec file in version 3 of the spec:

...
servers:
  slack:
    host: wss-primary.slack.com
    protocol: wss
channels:
  main:
    address: "/link/?ticket={ticket}&app_id={appID}"
    parameters:
      ticket:
        description: "your ticket ID. Ticket id can only be used for once."
        location: "$message.payload#/messageId"
        enum: ["a", "b"]
        default: ""
      appID:
        description: "Your slack app ID"
        enum: ["ffff", "ddddd"]
        default: ""
    bindings: 
      ws: {}
    messages:
      reactionAdded:
        $ref: "#/components/messages/reactionAdded"
...

it will fail because the parameters are going to be ignored.

Description

Glee should be able to handle the parameters.

If there is a location

parse the values from the message's payload or header and pass it to the operation function.
the new glee function type should be:

Attribute	Description
payload	The payload/body of the received event.
parameters	The parameters of the channel's address.
headers	The headers/metadata of the received event.
channel	The name of the channel/topic from which the event was read.
serverName	The name of the server/broker from which the event was received.

NOTE: glee should pick up the default value and use it if location is missing.

NOTE: if enum is specified, the parameter should be validated.

[p21nc3]

Hi @KhudaDad414, this can be fixed by making changes to parse parameters, having a new function type with attributes (payload, parameters, header, channels, servername). additionally enum validation & default value handling. here introducing an function type may or may not have regression in the framework, will run some test to validate that.
I would like to work on it, requesting to assign this issue to me.

[KhudaDad414]

@p21nc3 we do not assign issues. you can start working on it. if you need some help please let me know.

[KhudaDad414]

@p21nc3 I have started working on the issue here: #551 please check it out and leave some feedback.

[KhudaDad414]

/progress 60
partially implemented in #551

[asyncapi-bot]

🎉 This issue has been resolved in version 0.30.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀