Context Navigation

Changes between Initial Version and Version 1 of Ticket #37369, comment 3

initial	v1
1		Have we considered adding a new `transaction` API that implements the current behaviour instead of taking it away entirely?
	1	Have we considered adding a new `transaction` API replacement that implements the current behaviour instead of taking it away entirely?
2	2
3	3	I understand the rationale for defaulting to having `on_commit` raise when called outside of a transaction (mainly due its name) but I believe there is nonetheless merit in having a public API that allows the conditional deferring of an operation in code paths that may or may not be called within a transaction. It feels like a common enough pattern not to warrant making an explicit `in_transaction` check this is needed?