| Age | Commit message (Collapse) | Author |
|---|
|
This will hold our API token and provide methods to make API requests.
|
|
Set up the code to make a request to the Meetup API. Still needs an API
key, and we need to call the function correctly in `write_feed`.
|
|
|
|
Eventually, I want this function to make a request to the Meetup API and
return a `Vec` of `Event`s.
For now, though, so we can test things out, use our test JSON file
instead of a real web request.
|
|
This uses the RSS crate to build a new channel with items corresponding
to the given `Event`s. It needs to be fleshed out a little, but this is
the basic idea.
|
|
* Add an additional `Event` to the list of expected events to give us
more than one to test with.
* Remove all but the first two events from the JSON test data so we
don't have to reproduce all of those events in our test code.
|
|
* Derive `Deserialize` on our `Event` type
* Use Serde to parse a `Vec` of `Event`s that we can return from the
function
* Return a `Result` from the function to handle Serde errors
|
|
So we can derive `Deserialize` on our `Event` type.
|
|
A bunch of the descriptions had double quotes in them (`"`) that weren't
escaped. Escape these to make the JSON valid.
|
|
Add a couple function skeletons. Write the beginning of a test for the
function that parses a JSON string to a list of `Event`s.
In order to do the test, needed to derive `Debug` and `PartialEq` on
`Event`.
|
|
Include some fields that seem interesting. Also leave a note that we'll
want to create a new struct for `Venue` because this is a sub hash in
the JSON response.
|
|
For deserialising JSON from the API to a struct.
|
|
This comes from:
https://api.meetup.com/find/upcoming_events?&sign=true&photo-host=public&page=20
Grabbed from the browser API console.
We'll use this for writing unit tests.
|
|
|
