yeroc
Hello all!
A bit stumped on interpreting how to parse and extract my desired data from an API’s response with HTTPoison and Poison. I think I’m missing something simple.
Let’s say I want all the applicant names from “https://data.sfgov.org/resource/jjew-r69b.json?” .
In IEx-
iex(1)> res = HTTPoison.get! "https://data.sfgov.org/resource/jjew-r69b.json?"
%HTTPoison.Response{
body: "[{\"dayorder\":\"3\",\"dayofweekstr\":\"Wednesday\",\"starttime\":\"1PM\",\"endtime\":\"3PM\",\"permit\":\"19MFF-00079\",\"location\":\"1377 FELL ST\",\"locationdesc\":\"1:05pm-3:00pm\",\"optionaltext\":\"Cold Truck: Pre-packaged sandwiches, snacks, fruit, various beverages\"...
iex(2)> body = Poison.decode! res.body, keys: :atoms
%{
addr_date_create: "2017-07-31T15:11:15.000",
addr_date_modified: "2017-08-01T10:49:12.000",
applicant: "Bonito Poke",
block: "3736",
cnn: "107000",
coldtruck: "N",
dayofweekstr: "Wednesday",
dayorder: "3",...
iex(3)> (hd body).applicant
"Liang Bai Ping"
As you can see from the JSON in the link, this is indeed the head, coming back to me in a string as I want after a bit of manipulation through HTTPoison and Poison. How would I go about calling and returning all of the heads and not just the head or tail?
Enum.map gives me nil
iex(4)> Enum.map(body, & &1["applicant"])
[nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil,
nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil,
nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil,
nil, nil, ...]
Thanks for any help ![]()
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
cloudytoday
In your Poison.decode! call you’re specifying
keys: :atomswhich constructs the resulting maps’ keys as atoms and not strings, but in yourmapcall you’re providing a function which retrieves the field as it was a string (& &1[“applicant”]). I would recommend removing thekeys: :atomsfrom the Poison.decode! call. Alternatively, you can do the same but with& &1.applicant.yeroc
Ah yes! I got a bit turned around in the layers of changing the data. Thank you! Not sure what you mean by
?
cloudytoday
Oh I just meant that the alternative solution, if, for some reason, you really need them as atoms, would be to keep the
keys: :atomsin the Poison call, and to just change the function in theEnum.mapcall so that it retrieves the atoms viamap.atom_fieldsyntax (it’s equivalent to some_map[:atom_key]). And if you don’t need them as atoms, then you can simply remove thekeys: :atomsfrom the Poison call.yeroc
Ah yes! Thanks for clarifying!
yeroc
@cloudytoday Related to this question, if you have any thoughts and care to share