-
Notifications
You must be signed in to change notification settings - Fork 131
Fixed a problem with x-wr-calname #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I'm looking forward to this fix, too. |
You can use my fork at : https://github.com/ctide/ri_cal in the mean time, which has this fix. |
Thanks ctide, using your fork has saved me a headache :) |
np! |
@rubyredrick could you accept this pull request, pretty please. |
Also having this problem. +1 |
Same issue here, should be merged in original repo. +1 |
Any idea why this isn't being merged? |
I have this problem too - accepting this pull request would be great, @rubyredrick |
Bump - thanks for this gem @rubyredrick, please merge this |
I was honestly worried that @rubyredrick wasn't okay, but his Twitter account has become active again and he's pushed to his dotfiles repo recently. Issues on this repo are now closed. Rick, please, this library implements a major RFC -- can you put out a call for co-maintainers and try to find someone else worthy of push access and gem releases if you're unable to keep up with maintenance? Thank you very much for all the work you've done. |
Pulled from rubyredrick#5.
Oh my gosh this finally got merged?! |
I was running into an issue where adding the x-wr-calname property was being returned as:
X-WR-CALNAME::Lifetracker
Which causes the calendar name to show up in apps as ':Lifetracker'. I added a spec for it, and fixed where you were adding the colon in. All the specs passed afterwards, so I have to assume this was only really affecting this one property.
Sorry about the context -> describes, my rspec didn't like them in that file for some reason!