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 space member panel issues #8300

Merged
merged 3 commits into from
Jan 24, 2023
Merged

Fix space member panel issues #8300

merged 3 commits into from
Jan 24, 2023

Conversation

JammingBen
Copy link
Collaborator

Description

  • Fix re-loading the space members panel
  • Fix disappearing groups after removing one group form a space

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests

@JammingBen JammingBen self-assigned this Jan 24, 2023
@@ -219,6 +220,9 @@ export default defineComponent({
this.isSharedWithOthersLocation ||
this.isSharedViaLinkLocation
)
},
spaceResource() {
return this.spaces.find((s) => s.id === this.highlightedFile.id)
Copy link
Collaborator Author

@JammingBen JammingBen Jan 24, 2023

Choose a reason for hiding this comment

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

Again it makes it so much more complicated that the sidebar sometimes uses the highlightedFile for showing and mutating resources, sometimes we use the provided displayedItem, and now sometimes the spaceResource. It would be so nice to have that reduced to one provided prop (either via provide or via props).

Copy link
Member

Choose a reason for hiding this comment

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

fully agree 😕 I'm in favour of provide/inject for the data context of the sidebar. With props it'd be a pretty heavy cascade in some cases.

@@ -88,8 +88,10 @@ const mutations = {
state.spaceMembers = members
},
UPSERT_SPACE_MEMBERS(state, member) {
// group shares don't have the name prop... distinguish by shareType
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Distinction by shareType would be ideal, but I don't know if we need the server to adjust as well. Because the server currently handles space user- and group-shares via the same shareType: 7.

@ownclouders
Copy link
Contributor

Results for acceptance oCIS https://drone.owncloud.com/owncloud/web/32033/69/1

💥 The acceptance tests failed on retry. Please find the screenshots inside ...

webUISharingPublicExpire-shareByPublicLinkExpiringLinks_feature-L11.png

webUISharingPublicExpire-shareByPublicLinkExpiringLinks_feature-L11.png

💥 The oCISSharingPublic2 tests pipeline failed. The build has been cancelled.

@sonarcloud
Copy link

sonarcloud bot commented Jan 24, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

11.1% 11.1% Coverage
0.0% 0.0% Duplication

@kulmann kulmann merged commit 983865b into master Jan 24, 2023
@delete-merged-branch delete-merged-branch bot deleted the fix-space-member-panel-issues branch January 24, 2023 13:07
@micbar micbar mentioned this pull request May 3, 2023
89 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants