No description
I added in the translations the behavior of collect translations for; - Workflow Actions - Workflow States - Custom Fields This patch make sense when I'm translating a single app without revisions in ERPNext or Frappe translations. Using a patched version of the translation portal I'm being able of translate a single app, and I found that in these cases workflows actions/states are missed, and Custom Fields too, the actual behavior ensure that : - Workflow based messages will be exported first based on the doctype - Workflow based messages will be exported based on app only if the workflow is a fixture - Custom Fields messages will be exported based on app only if the custom field is a fixture. Note: Messages based on fixtures, will check a presence of a filter, if nothing is return this patch will understand that everything will be exported. |
||
|---|---|---|
| ci | ||
| frappe | ||
| test_sites | ||
| .gitignore | ||
| .travis.yml | ||
| attributions.md | ||
| CONTRIBUTING.md | ||
| hooks.md | ||
| license.txt | ||
| MANIFEST.in | ||
| README.md | ||
| requirements.txt | ||
| setup.py | ||
| socketio.js | ||
Frappe Framework
Full-stack web application framework that uses Python and MariaDB on the server side and a tightly integrated client side library. Built for ERPNext
Installation
Website
For details and documentation, see the website
License
MIT License
