COUNTER: test counter with recurring events

[chibenwa]

• COUNTER to CANCEL a recurrence
• COUNTER to add an override to a recurring event
• COUNTER to change the RRULE

Verify wich mail is sent in each case and ensure it brings sufficient details.

Ensure that "APPLYING" the proposal in TMail result in correct state.

Please @hungphan227 ...

[chibenwa]

Openpaas currently apply this for 1 instance wich works

Let's cover this explicitly with tests...

[hungphan227]

Tried COUNTER to change the RRULE on linagora env (change rrule count from 3 to 4):

• Email was sent. The ics file content is correct. However, the change detail in the display is not correct (nothing about rrule or rrule count):

• When clicking on yes button, tmail backend failed to process the request:

{
    "sessionState": "2c9f1b12-b35a-43e6-9af2-0106fb53a943",
    "methodResponses": [
        [
            "CalendarEventCounter/accept",
            {
                "accountId": "585402a3b8f0b72a30decc26bb71b46de3f56185f8bfbad616f599663f21796a",
                "accepted": [],
                "notAccepted": {
                    "ead41300-268c-11f1-b273-ffaed109ee17_4": {
                        "type": "serverFail",
                        "description": null
                    }
                }
            },
            "c0"
        ]
    ]
}

ics file in mail:

meeting (1).ics.txt

[hungphan227]

The same error occurred for case COUNTER to CANCEL a recurrence (adding EXDATE)

[hungphan227]

case "COUNTER to add an override to a recurring event" is working fine (this case can be easily reproduced by proposing change to one instance of recurring event on UI)

[chibenwa]

Please:

• Open a PR testing this in integration-testing
  ~~ - [ ] Please open a twake calendar side service ticket detailing RRULE + EXDATE templates and writes fixes for the email templates~~
  ~~ - [ ] Please open a tmail-flutter tiicket detailling how it looks like with EventCalendar/parse and what needs to be adapted.~~

Thanks.

[chibenwa]

Daily notes: we would not implement recurring upgrades on the front.

Let's just ensure the ITIP goes fine (integration testing). If we need we would plan wmore work on the topic but this is not needed today

[hungphan227]

Daily notes: we would not implement recurring upgrades on the front.

Let's just ensure the ITIP goes fine (integration testing). If we need we would plan wmore work on the topic but this is not needed today

So we just need to write tests in twake-calendar-integration-test to ensure that sabre produce the right message in calendar:event:notificationEmail:send?

[chibenwa]

So we just need to write tests in twake-calendar-integration-test to ensure that sabre produce the right message in calendar:event:notificationEmail:send?

No not even.

Actually I'll just close this: nobody implement that edge case...

[chibenwa]

Thanks for having a look.