-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Send out mail when recurring meeting template completed #17492
base: dev
Are you sure you want to change the base?
Conversation
0d62ea4
to
9921781
Compare
Caution The provided work package version does not match the core version Details:
Please make sure that:
|
1 similar comment
Caution The provided work package version does not match the core version Details:
Please make sure that:
|
The version warning is correct, but as the feature is developed behind a feature flag, it can already be merged in 15.2 |
service.generate_series | ||
end | ||
|
||
result | ||
.on_failure { |call| render_500(message: call.message) } | ||
.on_success do |call| | ||
send_data call.result, filename: filename_for_content_disposition("#{@recurring_meeting.title}.ics") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a question: when we generate an ical for a single occurence, should we also include that info in the filename?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes good point, I'll add that
@@ -67,7 +67,7 @@ def add_attendees(event, meeting) | |||
end | |||
|
|||
def ical_uid(suffix) | |||
"#{Setting.app_title}-#{Setting.host_name}-#{suffix}".dasherize | |||
Digest::SHA256.hexdigest "#{Setting.app_title}-#{Setting.host_name}-#{suffix}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will change the identifier of all existing meetings. Have we checked what the calendars do in this case or if it will duplicate calendar entries?
@@ -105,6 +118,7 @@ def occurrence_event(schedule_start_time, meeting) # rubocop:disable Metrics/Abc | |||
e.dtend = ical_datetime meeting.end_time, tzid | |||
e.url = url_helpers.project_meeting_url(meeting.project, meeting) | |||
e.location = meeting.location.presence | |||
e.sequence = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the specs the sequence should be increased every time the calendar event is updated, right? We do have a lock_version
on the meeting. Should we maybe use that as the sequence number?
Ticket
https://community.openproject.org/projects/meetings-stream/work_packages/60200/activity?query_id=5640