We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi @wookay,
I've updated to 0.4.1 but when receiving a JSON payload, it seems like the payload is not being parsed correctly. I followed this example https://github.com/wookay/Bukdu.jl/blob/master/examples/rest/ex2.jl
The JSON payload is something like this:
{ "simulation":{ "id":5927, "withdrawal_strategy_frequency": 1 } }
and it is being parsed to this type
Assoc(Pair{String,Any}["simulation"=>(id = 5927, withdrawal_strategy_frequency = 1))]
Instead of something like:
(simulation = (id = 5927, withdrawal_strategy_frequency = 1)))
Is there any reason why it might happen this?
The text was updated successfully, but these errors were encountered:
because the conn.params is a type of Assoc sometimes it's useful with undefined names like
conn.params
Assoc
@info :payload (c.params.message, c.params.x, c.params.y)
if you want to decode the request body directly, try this way
using JSON2
function create(c::RESTController) json = JSON2.read(IOBuffer(c.conn.request.body)) @info :json json end
Sorry, something went wrong.
in Bukdu v0.4.2, you could plug(Plug.Parsers, :json => Plug.ContentParsers.JSONDecoder, parsers=[:json]) see https://github.com/wookay/Bukdu.jl/blob/v0.4.2/examples/rest/ex3.jl
plug(Plug.Parsers, :json => Plug.ContentParsers.JSONDecoder, parsers=[:json])
No branches or pull requests
Hi @wookay,
I've updated to 0.4.1 but when receiving a JSON payload, it seems like the payload is not being parsed correctly. I followed this example https://github.com/wookay/Bukdu.jl/blob/master/examples/rest/ex2.jl
The JSON payload is something like this:
and it is being parsed to this type
Instead of something like:
Is there any reason why it might happen this?
The text was updated successfully, but these errors were encountered: