No description
In large threads, this leads to snowballing of replies, sometime even reaching more than 5 million characters. Email threads are already maintained in ERPNext, and modern clients are capable of maintaining threads. The only purpose it serves is maintain threads for text based email client, and I think we should ignore that use case, for improved user experience for Frappe/ERPNext users. |
||
|---|---|---|
| .github | ||
| ci | ||
| frappe | ||
| rollup | ||
| test_sites | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .travis.yml | ||
| attributions.md | ||
| CODE_OF_CONDUCT.md | ||
| hooks.md | ||
| LICENSE | ||
| Makefile | ||
| MANIFEST.in | ||
| node_utils.js | ||
| package.json | ||
| README.md | ||
| requirements.txt | ||
| setup.py | ||
| socketio.js | ||
| yarn.lock | ||
Full-stack web application framework that uses Python and MariaDB on the server side and a tightly integrated client side library. Built for ERPNext
Table of Contents
Installation
Contributing
Website
For details and documentation, see the website https://frappe.io
License
This repository has been released under the MIT License.