- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
fix(dav): Allow underscores on custom links #51715
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
Conversation
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
| /backport to stable31 | 
| This doesn't make sense, because creating custom links with underscores is not allowed in the first place: 
 | 
| Hum. Then 2 ways here, either allow it (I don't see a valid reason why not, but correct me), or validate input and clearly states that _ is not allowed. | 
| Well I'm wondering how we even received such a bug report, given that it's not allowed to create custom links with underscores. To me it only makes sense if we either miss the validation in some cases (maybe when updating the share?) or the report manually edited the database (and thus created an invalid report). I'm fine with allowing underscores though, I don't see why we should allow them. | 
| I agree with Kate and think we should do both 
 | 
| 
 Those links were created with the 3rdparty app  | 
| @kesselb comment also says: 
 | 
| I believe the user meant that they can still create share links with underscores using the cfg_share_links app. This app is available for Nextcloud 31 and is enabled according to the system report. The custom share link feature is disabled by default, so the user might not have realized they were using the app instead of the built-in approach. I wanted to clarify that the input validation for our custom share link feature is not broken and doesn't need fixing. If we want to allow underscores, continuing with this PR should be fine. | 
| I agree with @kesselb, but since there is nothing against allowing underscores we should just merge this PR. | 
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.
LGTM but did not test
Checklist