You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our code uses a bunch of ctx, whether it is updating the canvas, or drawing overlays on it. However, our usage of ctx varies heavily from place to place, using a very inconsistent combination of both this.ctx and canvas.getContext('2d'). This is partly a fault on TypeScript, as if canvas.getContext('2d') returns a ctx, then there's no way that it can return anything else unless a previous type of context was acquired from the ctx. I propose that eventually (definitely not right now), we should cleanup the code and decide how exactly we want to use this.ctx going forward.
The text was updated successfully, but these errors were encountered:
Our code uses a bunch of
ctx
, whether it is updating the canvas, or drawing overlays on it. However, our usage ofctx
varies heavily from place to place, using a very inconsistent combination of boththis.ctx
andcanvas.getContext('2d')
. This is partly a fault on TypeScript, as ifcanvas.getContext('2d')
returns actx
, then there's no way that it can return anything else unless a previous type of context was acquired from thectx
. I propose that eventually (definitely not right now), we should cleanup the code and decide how exactly we want to usethis.ctx
going forward.The text was updated successfully, but these errors were encountered: