tl;dr A hypothetical extension for mountebank could supply over the wire Equiv

mountebank extensions about mountebank HOT 4 CLOSED

bbyars commented on May 22, 2024

mountebank extensions

from mountebank.

Comments (4)

bbyars commented on May 22, 2024

I definitely like the idea. I think it's worth playing with how to represent this in the RESTful API. I didn't completely follow how the schema gets to mountebank in your example above, but given the AutoFixture-like response (AutoFixture is great, btw), it somehow needs to know how to generate the response. One idea could be as a different behavior with the schema inside the behavior definition:

{
    "port": 4545,
    "protocol": "http",
    "stubs": [
        {
            "responses": [
                {
                    "is": {
                        "statusCode": 200,
                        "body": "{\"id\": #{id}, \"name\": \"#{name}\"}"
                    },
                    "_behaviors": {
                        "generate": {
                            "id": {
                                "type": "number"
                            },
                            "name": {
                                "type": "string"
                            }
                        }
                    }
                }
            ]
        }
    ]
}

That has the advantage of working with other content types (e.g. XML) and other response fields (e.g. TCP data and HTTP statusCode) in a consistent way. If more robust generation is required (including randomly including/excluding optional fields), maybe:

{
    "port": 4545,
    "protocol": "http",
    "stubs": [
        {
            "responses": [
                {
                    "is": {
                        "statusCode": 200,
                        "body": "#{order}"
                    },
                    "_behaviors": {
                        "generate": {
                            "order": {
                                "type": "json",
                                "fields": [
                                    {
                                        "name": "id",
                                        "type": "number"
                                    },
                                    {
                                        "name": "name",
                                        "type": "string",
                                        "required": false
                                    }
                                ]
                            }
                        }
                    }
                }
            ]
        }
    ]
}

Definitely open to suggestions - did you have other ideas on how to structure the API?

from mountebank.

moodmosaic commented on May 22, 2024

No, as far as I can tell - Stub resolvers decorated with a hypothetical new behavior sounds great :) I think create or build are probably more precise names for this particular behavior definition.

from mountebank.

bbyars commented on May 22, 2024

Sounds good to me. If you're still interested in working on it, let me know if you need any help getting started. Definitely open to questions or even a skype if it helps.

from mountebank.

moodmosaic commented on May 22, 2024

Sounds good! Thanks, I will let you know! It might take me a couple of days before I open a pull request.

from mountebank.

Recommend Projects

mountebank extensions about mountebank HOT 4 CLOSED

Comments (4)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent