This week in the Sets series, we’ll look at
It does the same thing as
List.filter, except using our sets.
We’ll have it take a function that checks whether we should include a value and use the output of that function to filter the values from the set.
You’ve modeled your data exactly how it should be, and everything’s working fine.
Now it’s time to finish your JSON Decoder, but certain fields are strings where in your Elm code they’re complex data types!
This happens most often with dates, but tagged unions have this problem too.
In 0.17 we had
customDecoder, which could turn any
Result String a into a
Decoder a, but it went away in 0.18.
So… what do we do?