David Arnold

I've added a unit example of how the new datastructure can be worked with to the end of the PR description. The key is the addition of `net_amount` so that...

@ruthra-kumar even if we wouldn't be able to merge it right away, could we lock in an eventual agreement on the design principle, namely: - Extension of the datastructure by...

Thanks @ruthra-kumar I've added a priority developer SLA pledge to the beginning of the PR description for the next two weeks.

Does this migrate properly (between Data & Phone)? - to keep the diff-load low, consider to use the framework to update the json file (also sets the modified bit). Or...

Especially transaction heavy apps like ERPNext are essentially, for the most part, a doctype cast chain or even network (because they can branch and merge). Having a better framework-mediated shared...

I further hermit-brainstorm that, on this basis, custom-made static code analysis tools would be able to draft sections of functional system documentation (e.g. by extracting conventionalized docstrings alongside the doctype...

https://github.com/frappe/frappe/pull/27751 discusses a similarly conformed problem in the context of workflow transition. There, specifically: functional and security-wise inappropriateness of a broad `ignore_permissions=True` -type permission context across a domain boundary. cc...

# Enhanced DocumentProxy for Jinja Templating This PR, over its evolution, introduces significant improvements to the `DocumentProxy` class, enhancing its functionality and versatility in Jinja templating scenarios. These change provide...

# Enhanced EDI XML Invoice Generation with CustomDocumentProxy This PR introduces the possibility to construe a `CustomDocumentProxy` class to handle complex EDI scenarios, specifically for generating XML invoices with data...

## Adding a `DocumentProxy` value cache >[!NOTE] > This scenario has an async fetch via a _Virtual DocType_ > Even in the without value cache, this is being cached to...