realdah / simple-json-replay-server Goto Github PK

Maybe make the README example more clear by changing:

you can hit http://localhost:8008/test to see the result

to

you can hit http://localhost:8008/test?param1=value1%20to%20be%20matched&param2=value2%20to%20be%20matched to see the result

Hi Realdah,

I am a great fan of this library and I use it a lot in my current projects. I had a small suggestion like in general we will not use exact data in post request I will change continuously based on data.
why can we implement pattern matching instead of exact match in the data field, actually it helps developers a lot while doing form operations? for that, I have written a logic in utils.js file in your code which is working fine as expected for me. please add the below code at line 45 to get the solution.

else if(((typeof value) === 'string') && value.startsWith("/")){
if(fullObjectValue.match(value.substr(1, value.length-2))){
return false;
}else{
match = -1;
return true;
}
}

and mock json file:

{
"request" : {
"path": "test2",
"method": "post",
"body": {
"name": "Realdah",
"password": 1234,
"message": "/^[A-Z]+[A-Z]$/"
}
},
"response" : {
"status" : 200,
"data" : {
"message" : "you can see this because you used post method with pattern matching data",
"key" : "this is a post example with pattern matching data"
}
}

}

please follow below link for screenshots:

Thanks and Regards,
Viswa.

Note: it might be best if u have done the same implementation for query parameters also.

Definitely after adding these features this library will become so popular on all nodejs frontend technologies :):)

Hello,

Given the 2 following json files, the exact path does not take the precedence if it was registered before:
an.example.query.json
{
"request" : {
"path": "testTest"
},
"response" : {
"status" : 200,
"data" : {
"message" : "you can see this because you used the path 'testTest'"
}
}
}

example.query.json
{
"request" : {
"path": "test"
},
"response" : {
"status" : 200,
"data" : {
"message" : "you get default result. let's try http://localhost:8008/test?aa=123 or http://localhost:8008/test?bb=123 to see what's happen"
}
}
}

When targetting localhost:4200/testTest, I would expect to get the response "you can see this because you used the path 'testTest'"", instead I receive "you get default result. let's try http://localhost:8008/test?aa=123 or http://localhost:8008/test?bb=123 to see what's happen".

It happens because the 2 paths are matched because on line#13 of match.js indexOf is used. Then there is no score on the path itself. Therefore the last one registered will be used.

One way to fix it would be to add a score when the path match exactly with the request.

Best Regards,
Kevin.

Hi,

would it be possible to add cookie support to your mock server? I would like to have the mock service read a cookie and use as a signature to mock out a correct response based on data embedded in the cookie.

Thanks