| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Previously we used midnight, but this meant that the entire day
specified by `end_date` would be excluded, which is counterintuitive.
Instead use a second before midnight to include the rest of that day.
|
|
Instead of doing `use meetup::client::Client`, do `use meetup::Client`.
Makes it less redundant.
|
|
Make these values user-modifiable finally.
|
|
Since we've set up required arguments, 'getopts' fails fast and
complains about missing required args even if the only one used was `-h`
or `--help`. Why should you care about required arguments? You wanted
help in the first place, how are you going to know?
Thankfully, this message from 'prasannavl' pointed me in the right
direction:
https://github.com/rust-lang-nursery/getopts/issues/46#issuecomment-343842947
If there's an option parse failure, we can just look for the help flags
in the args vec to see if we should display the help.
|
|
These will be passed to `build_rss::write_feed`.
|
|
Well, turns out that the RSS item `description` field uses HTML, so my
`\n`s didn't actually change the formatting in a real RSS reader. Use
HTML tag formatting instead to get our description header with date and
venue to look right.
|
|
If either the description or both the date & time and venue were empty,
a couple of newlines would unnecessarily be added to the `Item`
description. This gets rid of them.
|
|
Move the join logic from `description_header` into a new function so we
can reuse it.
|
|
Instead of the verbose and unclear appending, use a `join` to add the
newline. Filter out empty strings to ensure the newline doesn't get
added if any of `where` or `place` are empty.
Needed to convert the slice strings to owned strings to deal with this
error:
error[E0599]: no method named `join` found for type `std::vec::Vec<&std::string::String>` in the current scope
--> src/meetup_rss.rs:92:10
|
92 | .join("\n")
| ^^^^
|
|
|
|
These were in-progress development ideas that have been superseded.
|
|
|
|
This function will format a string containing a date and venue for
inclusion in the description of an RSS `Item`.
Added a `derive(Clone)` on `Venue` in order to be able to clone it to
use its fields in the function.
|
|
This allows us to deserialise the venue location for events and include
it in the RSS items.
|
|
Now that the `description`, `local_date`, and `local_time` fields are
`Option` types, we need to update the tests to reflect this or they fail
terribly.
I made the change in aa0190279db75f75210f5279afaa62178b242837 but forgot
to update the tests.
|
|
* Take a date formatted in `%Y-%m-%d` and append the extra `THH:MM:SS`
that the Meetup API requires. We'll just be taking a regular string
from a user-inputted command line argument instead of a real date type
because it's easier and simpler.
* Use the name `end_date` to distinguish it from the `end_date_range`
parameter used by the API.
|
|
The description isn't very descriptive, but I'm a little tired right
now.
|
|
The Meetup API requires the `end_date_range` param to use this format,
otherwise it responds with an error.
Eventually we'll want to make this an actual time type and then
`strftime` it to this string.
|
|
Display all our errors this way.
|
|
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
|
