Skip to content

Server-side validation for whitespace in title - #7759

Merged
samin-z merged 2 commits into
mainfrom
fix/1512-validate-empty-title
Mar 16, 2026
Merged

samin-z merged 2 commits into
mainfrom
fix/1512-validate-empty-title

Conversation

@samin-z

@samin-z samin-z commented Mar 16, 2026 •

Copy link
Copy Markdown
Contributor
  • Target version: main

Summary

on Server-side it is possible to add whitespace for title.

TODO

Add extra validation for title to check it's not empty or whitespace.

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Tests (unit, integration, api and/or acceptance) are included
  • Documentation (manuals or wiki) has been updated or is not required

samin-z added 2 commits March 16, 2026 13:15
Signed-off-by: samin-z <samin.zavarkesh@gmail.com>
Signed-off-by: samin-z <samin.zavarkesh@gmail.com>
@samin-z
samin-z marked this pull request as ready for review March 16, 2026 12:27
@samin-z
samin-z merged commit 177076f into main Mar 16, 2026
44 checks passed
@samin-z
samin-z deleted the fix/1512-validate-empty-title branch March 16, 2026 12:40
@samin-z

samin-z commented Mar 17, 2026

Copy link
Copy Markdown
Contributor Author

/backport! to stable1.0

@backportbot

backportbot Bot commented Mar 17, 2026

Copy link
Copy Markdown

The backport to stable1.0 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable1.0
git pull origin stable1.0

# Create the new backport branch
git checkout -b backport/7759/stable1.0

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick e1ab13ce 79bcfaac

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/7759/stable1.0

Error: Failed to check for changes with origin/stable1.0: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@samin-z

samin-z commented Mar 19, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable33

@samin-z

samin-z commented Mar 19, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable32

@samin-z

samin-z commented Mar 19, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable31

@backportbot

backportbot Bot commented Mar 19, 2026

Copy link
Copy Markdown

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/7759/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick e1ab13ce 79bcfaac

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/7759/stable32

Error: Failed to check for changes with origin/stable32: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Mar 19, 2026

Copy link
Copy Markdown

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/7759/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick e1ab13ce 79bcfaac

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/7759/stable31

Error: Failed to check for changes with origin/stable31: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants