Mateusz Paprocki
Mateusz Paprocki
> As most of this PR (to me) looks like a refactor, it could be nice if you had a comment indicating this is the main change to fix the...
It would be good test changes in this PR, testing various combinations of the API for type errors only. There's `tests/unit/bokeh/test_layouts.py`, but due to lack of type information on models/properties,...
> I tried to add some tests but I think it is not what you are asking for. I don't know how to test for mypy type warnings or errors....
I'm referring to the top one, because there's another one on the page. Then on the search page there are three of them: 
Fill (and hatch) then stroke is the paint order we use across bokehjs. If we would go ahead with a different order in text painting, then we may also consider...
Hopefully this is only related to interactive tests. Synthetic events that are triggered by interactive testing utilities can exhibit unexpected behavior like showed.
If that won't work, an alternative is to `Proxy` model instances just in `CustomJS` and alike, and intercept appropriately attribute setting. In that limited context slowness of `Proxy` objects will...
What can be improved: - we need more granular verboseness, e.g. websocket tracing is only useful if debugging websockets - information should be printed on change, not on schedule -...
> I wanted to know if this issue is still there or already resolved? If not resolved can I start working on it? The issue is open and there are...
This is related to issue #5303.