| Age | Commit message (Collapse) | Author |
|---|
|
Use 'error-chain' here too. Seems like this will be a pretty useful
library.
Change the include in the 'meetup' `lib.rs` to allow us to export
`meetup::Error` instead of `meetup::errors::Error` to be consistent with
the error types of the other third-party libraries we're using.
|
|
|
|
I didn't pay attention when I wrote this, but that method actually
returns a `Result`, so we need to use it.
|
|
I had copied this from an example in the docs, but the compiler tells me
the `mut` isn't needed. Cool.
|
|
* Add a new module that contains a "main" library function that does the
integration for generating the feed and outputting it to STDOUT.
* Call this function from `main()` and have it output a real feed.
|
|
|
|
* Take a `Vec` reference instead of an object. This is the result of
messing around with calling the function in the test.
* Update the test to actually make assertions on the result of the
function.
|
|
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.
|
|
Use `reqopt` since this is a required option. Since the `opts.parse`
call will catch it if it isn't present earlier in the `main` function,
just unwrap it when extracting it.
|
|
|
|
Include an option to pass a Meetup.com API token (not saved yet).
|
|
Generated with:
$ cargo new --bin meetup-find-events-rss
|
