Enh/add recipient on blur

[GVodyanov]

Fix #9452

Adds mail recipients automatically when the NcSelect is deselected

[ChristophWurst]

I'm not sure I understand this trick. Is this for when you leave the input when a suggestion is shown in the dropdown?

[GVodyanov]

Took me a while to remember what was going on here too 😅

---

So (option === null || option === undefined) is needed because that function is called in two cases:

1. You selected one of the suggested options from the dropdown
2. You click outside the dropdown, so the recipient is added anyway

If you were to click on the dropdown without this check it would fire twice, once for the selection of the dropdown (@option:selecting), and once for the click closing the dropdown (@search:blur).

---

&& this.recipientSearchTerms[type] !== undefined
&& this.recipientSearchTerms[type] !== ''

Just normal checks

---

option = {}
option.email = this.recipientSearchTerms[type]
option.label = this.recipientSearchTerms[type]

Overriding the option parameter with not the dropdown content but the string content of the search of the NcSelect

this.recipientSearchTerms[type] = ''

Resetting the string content of the search of the NcSelect seeing as that string has already been added as a recipient

Hope this clears things up @ChristophWurst :)

[hamza221]

Tested ✅ maybe as a followup we check if the value is in email format, before adding the address

[GVodyanov]

Tested ✅ maybe as a followup we check if the value is in email format, before adding the address

Right, do we have a specific function for that? I wasn't able to find anything but it feels like we should have a standard for that, currently I just inserted a check on the @ character.

Also an issue I'm encountering is the search term being cleared even if the term wasn't added to the email list, I will investigate it further later but it's a little weird.

[hamza221]

I wrote a little hacky work-arround, But idk if it's really necessary. what do you think @ChristophWurst?
Feel free to discard it, If you find a better way

[GVodyanov]

I wrote a little hacky work-arround, But idk if it's really necessary. what do you think @ChristophWurst? Feel free to discard it, If you find a better way

Tested it, works well, and in my opinion it would do @hamza221

[kesselb]

/backport to stable3.7

[backportbot]

The backport to stable3.7 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable3.7
git pull origin stable3.7

# Create the new backport branch
git checkout -b backport/9566/stable3.7

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 9764b5ee

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/9566/stable3.7

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.