commit 8023d6481c
VRFS-3276 : Hook calendar creation into user controller API. Add test to verify.
commit 3a35002a46
VRFS-3276 : Calendar cleanup job
* Add cleanup method to calendar manager
* Create a daily job.
* Add calendar cleanup to that job.
* Add CRON entry
* Daily job/ calendar cleanup test cases
* Fix calendar manager spec for new required attribute
commit 3ff5910f1f
VRFS-3276 : Add a delete-calendar directive when RSVP is canceled.
VRFS-3276 : Include path to partial. This fails depending on the method used to start the web server.
commit d2441cbf57
VRFS-3276 : Test new calendar features. Use icalendar gem in test mode only to more deeply verify calendar in strict mode.
commit 9ac272a0fb
VRFS-3276 : Calendar manager updates to include manual calendars. Some refactoring to keep common stuff in one place.
commit b5d0c758f0
VRFS-3276 : Schema, model updates and new calendar model.
commit 20472b6b26
VRFS-3276 : Change initial submit behavior of RSVP dialog to display calendar info. The user can then close the dialog after this prompt.
commit 77c99103d0
VRFS-3276 : Calendar feed markup and styling. Included as partial.
commit e632f48600
VRFS-3276 : Routes and controller implementation of user calendar ICS feed, which uses calendar manager.
commit 21fd80a188
VRFS-3276 : Initial tests for calendar manager
commit 92a2524c65
VRFS-3276 : Calendar manager
* Streamline logic
* Enable recurring sessions through rrule
* Implement method to create ics feed for user
* Extract a type-safe scheduled duration method on music_session for
external and internal use.
commit b71ad3a4cd
VRFS-3276 : Include calendar manager
commit f8eaafd036
VRFS-3276 : Calendar Manager - initial checkin
* Create ICS events given individual parameters
* Create calendar from music session
* Also will create ICS “delete” events
* Additional attributes for band_type, band_status, concert_count,
add_new_members, play_commitment, touring_option, paid_gigs,
hourly_rate, gig_minimum
* For joined table musician_instruments, remove the hard requirement
that they be joined to a user, rather a “player” that is polymorphic.
* For joined table performance_stamples, remove the hard requirement
that they be joined to a user, rather a “player” that is polymorphic.
* For joined table online_presences, remove the hard requirement that
they be joined to a user, rather a “player” that is polymorphic.
* Change models as appropriate with new attributes and modify
belongs_to / has_many directives as necessary.
* Fix existing usages of user_id to work with polymorphic player_id.
* Fix tests that use user_id
* Add new tests that exercise online_presence, performance_samples, and
instruments that target a band, rather than a user.
Steven Miers
Seth Call