yarn lock wasn't updated correctly in last package.json update which
causes failure during update
[skip ci]
(cherry picked from commit 887d22cb1f)
Co-authored-by: Ankush Menat <ankush@frappe.io>
* perf: reduce DB calls made in `get_fetch_values`
* fix: ensure return value is same as before
* test: add test for `frappe.model.utils.get_fetch_values`
(cherry picked from commit f9bfbfec98)
Co-authored-by: Sagar Vora <sagar@resilient.tech>
Tuples need extra comma to make sure it's not treated as string.
[skip ci]
Co-authored-by: Sagar Vora <sagar@resilient.tech>
(cherry picked from commit 7452ac5d37)
RIP my cool handwritten AST code :'(
Few things to note:
1. Publicly documented APIs, they don't support capturing kwargs.
2. We can't use documented "lower level" APIs, we need to go _even lower_.
(cherry picked from commit 1425842ef0)
* Update Append to doctype description
Hello,
To append email to a doctype to enable automatic creation, there are two required fields listed

However, there is a third one required which is lacking in the above description (as seen below), because the email settings of the document must be enabled.

I propose to simply modify the sentence to the following :
Append as communication against this DocType (must have fields ("Status", "Subject") and "Sender" defined in the related doctype Email Settings).
To avoid any problem, in the code, it becomes the following :
Append as communication against this DocType (must have fields (\"Status\", \"Subject\") and \"Sender\" defined in the related doctype Email Settings).
The same must be applied in email_domain.json and in lots of csv in translations of course.
Pierre
* Update email_domain.json
* Updated sentence email account
* Updated sentence of email domain
* More brackets
* More brackets
* Typo
* Update email_account.json
* No dot
(cherry picked from commit 2d1fe02dba)
Co-authored-by: P-Godfroid <109596710+P-Godfroid@users.noreply.github.com>