[Bug] Odd response body for transactions

[alexghergh]

On the endpoint {{host}}/api/transactions/{{testGroupName}}/{{testBankName}}/new:

{
"statusCode": 400,
"message": "Cannot parse submitted transaction body!",
"error": "Unrecognized token 'alexghergh': was expecting ('true', 'false' or 'null')\n at [Source: (String)"{\n\t"amount": "150",\n\t"payee": alexghergh,\n\t"description": "This is a test of the transaction system. SomePayee adds 150 currency to the piggy bank.",\n\t"tags": "fun, test, transaction, tutorial, API"\n}"; line: 3, column: 21]"
}

[StormFireFox1]

Well, isn't this fun to read. (I'm kidding, no need for formatting :) )

On 19/06/06 05:09AM, Alexandru Gherghescu wrote: { -%<- "error": "Unrecognized token 'alexghergh': was expecting ('true', 'false' or 'null')

Well, ain't that interesting. Why does it think that 'alexghergh' would be a boolean value?

-%<- "payee\": alexghergh,\n\t\ -%<-

Well, as far as I can see here, there is no quotes surrounding "alexgergh", which I assume is the string you were attempting to pass in JSON. Although I think I might change this in the not-so-distant future, simply because it might be better to send the whole user JSON to this endpoint rather than add an extra query to the database on the server-side. As far as this issue is concerned, check to see if the lack of quotes was the problem. If it was, then great, we're done here.

…

-- Matei-Alexandru Gardus (Storm_FireFox1) https://stormhub.io

[alexghergh]

Indeed, the lack of quotes produced that kind of weird result.

Tried surrounding the name with quotes, and its a 500 server error given back.

[StormFireFox1]

On 19/06/08 01:05PM, Alexandru Gherghescu wrote: Tried surrounding the name with quotes, and its a 500 server error given back.

Can you send me an example so I can reproduce the bug? Currently the JSON you sent above does not cause any exceptions on my end. Send me a cURL command or perhaps a log file.

…

-- Matei-Alexandru Gardus (Storm_FireFox1) https://stormhub.io