availity/availity-ekko

Mock server simulating API rest services

availity-ekko's Issues

Update logger to match availity-workflow

switch to ESLint

Fails to respond with default response using array configuration

Navigating to:

http://localhost:3000/api/sdk/platform/v1/regions

Results in:

http://localhost:3000/api/sdk/platform/v1/null

add hapi plugin support

Remove readme gulp task

Default response fails unless params config is defined

"v1/path": {
  "file": "pong.json"
}

should respond with pong.json when request url is locahost.local/v1/path?a=b

sunset support for node 10.x

Allow headers to be set in responses

"v1/route8": {
    "file": "example1.json",
    "get": [
      {
        "file": "example2.json",
        "response": [
          {
            "status": 202,
            "file": "example3.json",
            "headers": {
              "Location": "/v1/route8"
            }
          },
          {
            "status": 201,
            "file": "example4.json"
          }
        ]
      }
    ]
  }

Decoding error with organizations endpoint

When the browser goes to decode the response from the organizations endpoint, there is a decoding error.

When trying to view the response in Fiddler, I receive this error:

The issue is resolved after I remove the compression middleware.

Middleware configuration doesn't support custom environments

In middleware/index.js:L9-11, the code is pulling in 3 environments (development, testing, and production); however, in server/index.js:L27-28, we pull the environment from the NODE_ENV variable. This variable can be set to anything the developer wants, but setting it to anything other than the 3 environments listed will result in an error:

TypeError: middleware[(environment || "development")] is not a function

The most flexible option would probably be to allow the developer to add their own middleware function for their environment.

Also, I don't believe the availity-toolkit scripts will run for staging and integration since there is no staging or integration middleware setup. I haven't tried though.

Proxy contexts don't trigger

Using the following configuration:

servers: {
  web: {
    host: '0.0.0.0',
    port: 8090
  },
  aries: {
    port: 8280,
    proxy: true,
    proxies: [
      {
        context: "/api",
        rewrite: {
          from: "^/api",
          to: ""
        }
      },
      {
        context: "/public/api",
        rewrite: {
          from: "^/public/api",
          to: ""
        }
      }
    ]
  },
  axi: {
    port: 8080,
    proxy: true,
    proxies: [
      {
        context: "/availity"
      }
    ]
  }
}

}

I can't get the proxy routes to fire. What appears to be happening is that by the time proxy.js gets the request URL to process, req.url already has the context stripped. It's getting /v1/blah instead of /api/v1/blah, which means the matcher never fires.

Asynchronous response not working.  Always returning same response

No matter what responses are configured, only the first file specified is returned.

Show routing table on startup

convert to Express middleware

Add multiple config files support

Currently routes are configured through routes.json file. It is good only for smaller size of apps. In a larger app where different teams develop different APIs, it becomes a pain to maintain this file. Merge conflicts occur very often. And this file gets easily corrupted by a bad merge - it has happened quite some times in our dev env, and when this happens, the app stopped working locally.

@bobbennett can correct me if I am wrong.

If routes can be configured in a dir instead of a single file, we can split up this file into multiple json configs where each team updates their own portion, things would become more manageable.

Add support for route matching using headers

No documentation on how to setup proxies for other environment

There is are examples on how to mock responses but not any examples how to point to actual services.

Options set at the method level are not used

Options set at the method level as seen below are not used. I can only set options such as status and latency at the resource path level.

{
  "resourcePath": {
  "get": [
    {
      "latency": 1000,
      "file": "resource-get.json"
    }
  ],
  "put": [
    {
      "status": 422,
      "latency": 10000,
      "file": "resource-put.json"
    }
  ]
}
}

Promise does not resolve for invalid routes

[15:23:57] [av-ekko] GET /api/v1/organizations/undefined 404 0.496
Warning: a promise was created in a handler but was not returned from it
    at tryOnImmediate (timers.js:534:15)
    at processImmediate [as _immediateCallback] (timers.js:514:5)

switch to ESLint

Add more params matching support

It would be nice to add more params matching support such as:

• regex
• pipe delimited string

For example, if I want to match a param season of Spring|Summer|Fall, currently it seems the only solution is to split them up:

{
    "get": [
        "file": "non-winter-response.json",
        "params": {
            "season": "Spring"
        },
        "file": "non-winter-response.json",
        "params": {
            "season": "Summer"
        },
        "file": "non-winter-response.json",
        "params": {
            "season": "Fall"
        }
    ]
}

It would be nice if we can do:

{
    "get": [
        "file": "non-winter-response.json",
        "params": {
            "season": "Spring|Summer|Fall"
        }
    ]
}