fix(files_sharing): add missing subtitle on search for share recipients

[luka-nextcloud]

• Resolves: [Bug]: Remote server name missing from search result in sharing tab #46444

Summary

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[Pytal]

We should rename the subtitle key in options to subname instead of reimplementing the option slot

[luka-nextcloud]

We should rename the subtitle key in options to subname instead of reimplementing the option slot

Changing subtitle to subname does not work. It is because subname is only visible on avatar size of 32 and above (https://nextcloud-vue-components.netlify.app/#/Components/NcListItems?id=nclistitemicon)

[Pytal]

Changing subtitle to subname does not work. It is because subname is only visible on avatar size of 32 and above (nextcloud-vue-components.netlify.app)

I see, in that case it is a bug in the lib so we should be increase it there to 32px + do the subname rename here

[luka-nextcloud]

Changing subtitle to subname does not work. It is because subname is only visible on avatar size of 32 and above (nextcloud-vue-components.netlify.app)

I see, in that case it is a bug in the lib so we should be increase it there to 32px + do the subname rename here

I made a PR on the lib side. We first need to check and release it.

[luka-nextcloud]

@juliushaertl Should we wait until the new version of the library is released?

[juliushaertl]

/compile amend /

[juliushaertl]

@luka-nextcloud maybe try to push the commit just with the src change and use the compile command if you can't get the local build to pass ci

[luka-nextcloud]

/compile amend /

[AndyScherzinger]

Since this is reported broken for v28+, can this be backported then @juliushaertl @luka-nextcloud ? Can't tell since it mentioned a lib change, so slightly more complex to do eventually.

[juliushaertl]

Yes, I'd leave that to @luka-nextcloud for the case he has ;)

[luka-nextcloud]

/backport to stable28

[backportbot]

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/46591/stable28

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/46591/stable28

Error: No changes found in backport branch

---

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