Skip to content
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

Fix share owner not being displayed in sharing tab #30266

Merged
merged 1 commit into from
Dec 16, 2021

Conversation

CarlSchwan
Copy link
Member

This only concerns subfolder and files inside a shared folder and is
used as fallback when the OCS api returns a empty result, because it
only works on the shared folder and not the content inside of it.
This unify the tab with the folder list.

This offers a less descriptive share information but making the
OCS api returns all the details even for the subfolder would very
probably be bad for performance (since we would need to fetch the shares
for all the parent folders until we found one or are in the root folder).

Signed-off-by: Carl Schwan carl@carlschwan.eu

@CarlSchwan CarlSchwan added the 3. to review Waiting for reviews label Dec 14, 2021
@CarlSchwan CarlSchwan added this to the Nextcloud 24 milestone Dec 14, 2021
@CarlSchwan CarlSchwan requested review from a team, PVince81, artonge and Pytal and removed request for a team December 14, 2021 12:36
@Pytal
Copy link
Member

Pytal commented Dec 14, 2021

/compile amend /

@nextcloud-command nextcloud-command force-pushed the fix/share-not-being-displayed-tab branch from 9b3234d to 71d2578 Compare December 14, 2021 21:15
@CarlSchwan CarlSchwan force-pushed the fix/share-not-being-displayed-tab branch from 71d2578 to ebc49a4 Compare December 14, 2021 21:15
@CarlSchwan
Copy link
Member Author

/compile amend /

Copy link
Member

@Pytal Pytal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the folder owner somehow it got to this state
image
due to this.fileInfo.shareOwnerId being undefined but not sure why 🤷‍♂️

@nextcloud-command nextcloud-command force-pushed the fix/share-not-being-displayed-tab branch from ebc49a4 to 5148c5f Compare December 14, 2021 21:26
@CarlSchwan
Copy link
Member Author

As the folder owner somehow it got to this state image due to this.fileInfo.shareOwnerId being undefined but not sure why man_shrugging

Yeah I noticed that and forgot to push the change. Now I need to fix the conflict and compile the assets again

@CarlSchwan CarlSchwan force-pushed the fix/share-not-being-displayed-tab branch from 5148c5f to e577308 Compare December 14, 2021 21:51
@CarlSchwan
Copy link
Member Author

/compile amend /

This only concerns subfolder and files inside a shared folder and is
used as fallback when the OCS api returns a empty result, because it
only works on the shared folder and not the content inside of it.
This unify the tab with the folder list.

This offers a less descriptive share information but making the
OCS api returns all the details even for the subfolder would very
probably be bad for performance (since we would need to fetch the shares
for all the parent folders until we found one or are in the root folder).

Signed-off-by: Carl Schwan <carl@carlschwan.eu>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@nextcloud-command nextcloud-command force-pushed the fix/share-not-being-displayed-tab branch from e577308 to 9c4cf73 Compare December 14, 2021 22:00
@skjnldsv skjnldsv merged commit 55219ac into master Dec 16, 2021
@skjnldsv skjnldsv deleted the fix/share-not-being-displayed-tab branch December 16, 2021 07:50
@skjnldsv
Copy link
Member

Backports?

@CarlSchwan
Copy link
Member Author

/backport to stable23

@CarlSchwan
Copy link
Member Author

/backport to stable22

@CarlSchwan
Copy link
Member Author

/backport to stable21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants