jerch
jerch
Coming from #120 - we prolly want some sort of a setting/argument around computed fields to specify a certain manager to be used. This needs some thinking how to shape...
The f-expression restriction in methods is really nasty. We should investigate, when and how it is safe to declare expression values in computed field methods and document that more clearly....
These are somewhat hard to test automatically with all their arguments (thus currently skipped in coverage). Needs a good story how to approach them from unit tests.
Currently db interactions simply route to 'default' connection without any means to change that through the API. TODO: - investigate on custom db routers, esp. for the read vs. write...
In `bulk_updater` we do a DISTINCT on every query in question. This is needed to avoid updating 1:n relations over and over. Issues with this: - DISTINCT is placed there...
Currently coveralls marks a CI run as failed for a tiny decrease in coverage. Check if there is a threshold setting to get it less noisy.
Shall fix #56. This is just a proof of concept currently with hacked in signal dispatching for `update_dependent`. TODO: - apply data aggregation on all resolver parts including handler code...
Coming from the discussion in #49. We should establish some way of getting notified when CFs are getting updated by the resolver. There are several ways to achieve this, mainly...
RIS slipped somehow through, when doing the VT function docs.
Currently it is almost impossible for app side to reliably figure out xterm.js as TE or its version. Linked to that are supported/unsupported features, or additions from addons. **Suggestion** Establish...