-
Notifications
You must be signed in to change notification settings - Fork 157
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
feat: remove internal link type #11553
Conversation
779708f
to
b1f043f
Compare
@tbsbdr @kulmann There is one edge case when the user doesn't have the permission to create public links. In the past, creating internal links was still possible. With this change though, those users can't create links at all, which is a bit tricky because of the "Copy link" quick action. We can easily check if the resource as a link share and then decide whether to display the quick action or not. But we can't check if the resource has a quick link. And since the quick action is designed to only copy quick links, this results in an issue when a resource has a normal link, but not a quick link. We could change to quick action to factor in regular links as well. Or simply ignore this edge case. |
I'd opt to make the permalink the default quickaction link. we already talked about it some time ago. what do you think @kulmann ? |
default was in always use the permalink?! If I remember correctly I advocated to kill the quick link concept entirely and instead just use any first link that can be found on the resource. If there is none -> permalink. Since this PR is about removing the internal link type, a good step in between is to copy the permalink when the user isn't allowed to create a public link. Not so sure about always copying the permalink as the only option for the quick action. 🤔 |
Lets always use the perma link in the quickaction. ok @JammingBen @AlexAndBear @kulmann ? |
What about the action in the right-click context menu? We have the same problem here. Should it also just copy the permanent link? |
Removes the internal link type since the permanent link makes it obsolete. Existing internal links still resolve correctly to ensure backwards compatibility.
IMO yes. Maybe it makes sense to rename the |
Okay, so to get this straight: The only way to create a public link will be via the sidebar in the future - no more (quick-) action for that, right? I like that, in fact that's what I was suggesting a few week ago. I just want to make sure we are all on the same page here, because I can certainly imagine that some users won't like it. |
Yep, discussed with Tobi yesterday, that we want to try exactly what you're describing. 👍 |
b1f043f
to
2b076b5
Compare
Removes the action in favour of the new action for copying permanent links.
2b076b5
to
82f2115
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely stunning 🤩
Description
Removes the internal link type since the permanent link makes it obsolete. Existing internal links still resolve correctly to ensure backwards compatibility.
Also removes the action in favor of the new action for copying permanent links.
Related Issue
Types of changes