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

Drive alias: one of the space does not open with the same alias #7715

Closed
ScharfViktor opened this issue Sep 29, 2022 · 1 comment · Fixed by #7725
Closed

Drive alias: one of the space does not open with the same alias #7715

ScharfViktor opened this issue Sep 29, 2022 · 1 comment · Fixed by #7725
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working

Comments

@ScharfViktor
Copy link
Contributor

related to #7430

Steps:

  • Create 2 spaces with the same name "new space"
  • rename one space to "renamed" space
  • try to open "new space"

Expected: "new space" space has been opened
Actual: "renamed" space has been opened

Screen.Recording.2022-09-29.at.14.47.46.mov
@ScharfViktor ScharfViktor added Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working labels Sep 29, 2022
@kulmann
Copy link
Contributor

kulmann commented Sep 29, 2022

Same as in #7714

This is a known regression from the drive alias PR. Since duplicate drive aliases are allowed it is not possible at the moment to know which of the spaces to open (applies for the files view and the trash bin of the space). You will only ever see the first space/trash with this drive alias. To fix this we need #6247 (next on my list to implement).

Of course a GA blocker. Let's keep this issue here open, as it shows pretty well what happens when not using ids for resolving spaces. The linked ticket only lists the requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants