Kj/wir 18 reloading wire conversation details

[LennardZieglerCONPORT]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

Once a meeting has been created in Outlook and Wire Meeting details have been added, the user can remove all mention of the link to the meeting in the location field and in the meeting's description.

If it was a mistake and the user wants to revert it, he can't regenerate the meeting invitation link or details by using the "Add Wire meeting Link" button. It will throw an error stating the meeting is already linked.

Solutions

Reloading Wire conversation details of the already created conversation in a meeting where it has been deleted and setting it again into the appointment.

Dependencies (Optional)

• fix(API access): Update API from v2 to v5 and add API Version as env #35

Needs releases with:

• GitHub link to other pull request

Testing

How to Test

Create an appointment and click "Add a meeting link." After that, delete the location and/or the body from the appointment. Click again on "Add a meeting link." The deleted part of the appointment should be reloaded.

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ KevinJaroschewskiCONPORT
❌ kevin.jaroschewski

---

kevin.jaroschewski seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}