elm - Json.Decode.Pipeline trouble with optional -


i'm having trouble decoding optional fields json string. trying decode "plannings" , planning can of 2 types, normal planning, or flex planning. if normal planning, have planning_id, if flex planning, have flexplanning_id. in record in store plannings, both planningid , fiexplanningid of type maybe int. 

type alias planning =     { time : string     , planningid : maybe int     , groupid : int     , groupname : string     , flex : bool     , flexplanningid : maybe int     , employeetimeslotid : maybe int     , employeeid : int     }

and here decoder use: 

planningdecoder : decoder planning planningdecoder =     decode planning         |> required "time" string         |> optional "planning_id" (nullable int) nothing         |> required "group_id" int         |> required "group_name" string         |> required "flex" bool         |> optional "employee_timeslot_id" (nullable int) nothing         |> optional "flexplanning_id" (nullable int) nothing         |> required "employee_id" int

however, decoder isn't accurately decoding , storing data json. here example. 1 piece of string returned request made application: 

"monday": [ { "time": "07:00 - 17:00", "planning_id": 6705, "group_name": "de rode stip", "group_id": 120, "flex": false, "employee_timeslot_id": 1302, "employee_id": 120120 }, { "time": "07:00 - 17:00", "group_name": "vakantie groep", "group_id": 5347, "flexplanning_id": 195948, "flex": true, "employee_id": 120120 } ],

this, however, result of decoder: 

{ monday = [   { time = "07:00 - 17:00"   , planningid = 6705   , groupid = 120   , groupname = "de rode stip"   , flex = false, flexplanningid = 1302   , employeetimeslotid = nothing   , employeeid = 120120 }  ,{ time = "07:00 - 17:00"   , planningid = nothing   , groupid = 5347   , groupname = "vakantie groep"   , flex = true   , flexplanningid = nothing   , employeetimeslotid = 195948   , employeeid = 120120    }  ],

as can see, in json, there 2 plannings, 1 planning_id , other flexplanning_id. however, in record produced decoder, first planning has both planningid , flexplanningid, whereas second has neither.

you need flip these 2 lines in decoder match order in defined:

|> optional "employee_timeslot_id" (nullable int) nothing |> optional "flexplanning_id" (nullable int) nothing

they defined in order:

, flexplanningid : maybe int , employeetimeslotid : maybe int

Comments

Post a Comment

Popular posts from this blog

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

i getting "__type": "com.amazon.coral.service#serializationexception" as reply in postman & in test console in api gateway trying post record directly dynamodb using api proxy services.. referring aws article - https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/ here's mapping { "tablename": "tablenamegoeshere", "item": { "id" : "$context.requestid" "eventname" : "$input.path('$.eventname')", "timestamp" : $input.path('$.timestamp'), "answers": "$util.parsejson($input.path('$.answers'))" } } update: did asked ... , worked if try add array of json objects gives me above same error - here's trying now. please - couldnt find on google well #set($inputroot = $input.path('$')) { "tablename": "answer", "item": {
Read more

asp.net - Problems sending emails from forum -

i have been redesigning site has message board, has been written guy looked after site. it has few problems , written in .asp , uses .mdb files database. you can see whole thing here . feel free post if helps, test thing have set using original files , new database. the basic problem when posts message, supposed email sent them, have posted it. when replies, originator supposed message, replier has been posted. i’d have thought @ point in process there should script/file in postmessage.asp? the postmessage.asp page below. <% option explicit %> <!-- #include virtual="common/adovbs.inc" --> <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="microsoft frontpage 4.0"> <meta name="progid" content="frontpage.editor.document"> <title>new page 2</title> <base target="_self"
Read more