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: fetch signature methods #4185

Merged
merged 2 commits into from
Dec 23, 2024
Merged

fix: fetch signature methods #4185

merged 2 commits into from
Dec 23, 2024

Conversation

vitormattos
Copy link
Member

When we make a patch at a signature request, the signature method need to be always returned and this continue was removing the signature methods from return object.

Side effects of previous code: When I make a patch of herself sign request, I can't sign the document if the file list wasn't updated because the signature methods is returned to each element when we are listing the files. With this change is possible to return the signature methods after I'm added to be a signer and go ahead to sign the document.

When we make a patch at a signature request, the signature method need
to be always returned and this continue was removing the signature
methods from return object.

Signed-off-by: Vitor Mattos <[email protected]>
@vitormattos vitormattos added this to the Next Major (31) milestone Dec 23, 2024
@vitormattos vitormattos self-assigned this Dec 23, 2024
@vitormattos
Copy link
Member Author

/backport to stable30

@vitormattos
Copy link
Member Author

/backport to stable29

@vitormattos vitormattos force-pushed the fix/fetch-signature-methods branch 2 times, most recently from 8eed393 to 835a691 Compare December 23, 2024 23:07
Signed-off-by: Vitor Mattos <[email protected]>
@vitormattos vitormattos force-pushed the fix/fetch-signature-methods branch from 835a691 to 047b89a Compare December 23, 2024 23:15
@vitormattos vitormattos merged commit b7b55bd into main Dec 23, 2024
61 checks passed
@vitormattos vitormattos deleted the fix/fetch-signature-methods branch December 23, 2024 23:36
@backportbot-libresign
Copy link

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

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

# Create the new backport branch
git checkout -b backport/4185/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick d31748bc 047b89a4

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

Error: Failed to push branch backport/4185/stable29: fatal: could not read Username for 'https://github.com': No such device or address


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

@vitormattos
Copy link
Member Author

/backport to stable29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 4. to release
Development

Successfully merging this pull request may close these issues.

1 participant