Pull data from Meetup API #4
Comments
woolsweater
pushed a commit
to woolsweater/pdxcocoaheads.com
that referenced
this issue
Aug 4, 2016
…ssing pdx-cocoaheads#4. Droplet.client makes the request to the Meetup API, which returns a list in JSON. The JSON is unpacked into instances of `MeetupEvent`. `MeetupEvent` currently stores just the fields known to be needed for the template, and implements `MustacheBoxable` so that it can be included directly in the rendering context. Created Mustache template and stylesheet for the page, with two filters to make numerical data look good. Added link to new page to homepage nav. Added basic testing for new functionality: Mustache filters and `MeetupEvent`. Needs further structural refinement: currently too much is done inside the route handler.
woolsweater
pushed a commit
to woolsweater/pdxcocoaheads.com
that referenced
this issue
Aug 24, 2016
The "/events" route handler now uses a MeetupAPI object, which makes the connection to api.meetup.com. The MeetupAPI.getUpcomingEvents() method pulls down future events. The events are provided by Meetup.com as a JSON array. The JSON objects are unpacked into a parallel array of MeetupEvent structs, which is passed back out to the route handler to be used as the context for the view. A private Configuration struct supplies MeetupAPI with the appropriate URL information. It gets the URL pieces from the Config/meetup.json file, accessing that file via the active Droplet's Config object: the Droplet aleady knows where the config files are, rather than us having to find them again. The Droplet's Config is passed in to MeetupAPI on its creation, which hands it off to its Configuration.
woolsweater
pushed a commit
to woolsweater/pdxcocoaheads.com
that referenced
this issue
Aug 24, 2016
The "/events" route handler now uses a MeetupAPI object, which makes the connection to api.meetup.com. The MeetupAPI.getUpcomingEvents() method pulls down future events. The events are provided by Meetup.com as a JSON array. The JSON objects are unpacked into a parallel array of MeetupEvent structs, which is passed back out to the route handler to be used as the context for the view. A private Configuration struct supplies MeetupAPI with the appropriate URL information. It gets the URL pieces from the Config/meetup.json file, accessing that file via the active Droplet's Config object: the Droplet aleady knows where the config files are, rather than us having to find them again. The Droplet's Config is passed in to MeetupAPI on its creation, which hands it off to its Configuration.
woolsweater
pushed a commit
to woolsweater/pdxcocoaheads.com
that referenced
this issue
Aug 24, 2016
The "/events" route handler now uses a MeetupAPI object, which makes the connection to api.meetup.com. The MeetupAPI.getUpcomingEvents() method pulls down future events. The events are provided by Meetup.com as a JSON array. The JSON objects are unpacked into a parallel array of MeetupEvent structs, which is passed back out to the route handler to be used as the context for the view. A private Configuration struct supplies MeetupAPI with the appropriate URL information. It gets the URL pieces from the Config/meetup.json file, accessing that file via the active Droplet's Config object: the Droplet aleady knows where the config files are, rather than us having to find them again. The Droplet's Config is passed in to MeetupAPI on its creation, which hands it off to its Configuration.
woolsweater
pushed a commit
to woolsweater/pdxcocoaheads.com
that referenced
this issue
Aug 24, 2016
The "/events" route handler now uses a MeetupAPI object, which makes the connection to api.meetup.com. The MeetupAPI.getUpcomingEvents() method pulls down future events. The events are provided by Meetup.com as a JSON array. The JSON objects are unpacked into a parallel array of MeetupEvent structs, which is passed back out to the route handler to be used as the context for the view. A private Configuration struct supplies MeetupAPI with the appropriate URL information. It gets the URL pieces from the Config/meetup.json file, accessing that file via the active Droplet's Config object: the Droplet aleady knows where the config files are, rather than us having to find them again. The Droplet's Config is passed in to MeetupAPI on its creation, which hands it off to its Configuration.
boek
added a commit
that referenced
this issue
Sep 20, 2016
Implement #4, "Pull data from Meetup API"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can get the data pretty easily form
We should create a nice component for the home page to get this data.
The text was updated successfully, but these errors were encountered: