Move x-remoteServers Configuration to glee.config.(js|ts)

[KhudaDad414]

Context

Currently, Glee specifies which servers are remote by using the x-remoteServers attribute in the AsyncAPI file. It is proposed to move this configuration to the glee.config.(js|ts) file, as this is a configuration specific to Glee, rather than to the API itself.

Current Implementation

In the current setup, the AsyncAPI file contains the x-remoteServers attribute:

x-remoteServers:
  - httpbin.org

Proposed Implementation

The new configuration would be part of the glee.config.(js|ts) file, making it more intuitive and aligned with other Glee configurations:

export default async function () {
  return {
    glee: { // Glee core configurations
      remoteServers: ["httpbin.org"],
      // ... other configurations
    },
    // ... other configurations...
  }
}

[afzal442]

Hi, is this related to code change to support the outcome and let logic do the work or just moving the config?

[KhudaDad414]

@afzal442 the logic works as explained. it parses it from the AsyncAPI file.

glee/src/registerAdapters.ts

Line 44 in 2b747d5

const remoteServers = parsedAsyncAPI.extensions().get('x-remoteServers')?.value()

we need to first change the code logic to get it from the config file and update the documentation as well.

[afzal442]

I think it is going to be tricky for me as it has to do sth like extracting the value from glee.confile file.

[ayush3160]

@KhudaDad414 , I would like to work on this issue.

[KhudaDad414]

During a recent discussion, it is clear that this specific piece of info is important to be where it is now.
why? At last, glee should be able to function only when it has the asyncapi.yaml file and the operation functions.
since this piece of information is critical for Glee to run, If we put it in the config file, then the config file also becomes a necessity and Glee has to rely on the config file as well, which is impossible in other environments like browser.

I suggest for now we keep it where it is.