-
Couldn't load subscription status.
- Fork 135
fix: check if template fields should be extracted #4713
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
153be00 to
045926a
Compare
045926a to
aaaafb6
Compare
|
This is obsolete with the slightly different approach in nextcloud/server#52514, right? |
aaaafb6 to
daa73bf
Compare
|
@juliusknorr Not necessarily. We still need to check |
daa73bf to
cc38527
Compare
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.
Small addition to account for compatibility, but otherwise 👍
The `BeforeGetTemplatesEvent` now has a property that allows us to check if the templates should be enhanced with fields or not. If so, then we extract the fields, if not, simply do not. Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>
cc38527 to
770287f
Compare
Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>
|
/backport to stable31 |
Summary
With the new server changes, we need to check if the event tells us to fetch the fields or not. If the fields should be extracted, then we do that. On the server side, this will only be triggered once the user makes a template selection, and only that template will be sent.
The documentation has been updated for the server pull request, and the
templates.spec.jstests have been expanded a bit in this pull request to verify that no template fields are extracted at first.Checklist