Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[ts] conflicting font types

See original GitHub issue

uPlot.Axis currently defines:

        font?: CanvasRenderingContext2D['font'];
        labelFont?: CanvasRenderingContext2D['font'];

While true for values passed into constructor, various callbacks actually need to deal with values processed by pxRatioFont(), which, it seems, actually has (non-null? not sure about that) return type [string, number, number].

Issue Analytics

State:
Created 2 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

1reaction

Venryxcommented, Oct 9, 2021

I unfortunately do not have the time/motivation for this right now. I can provide technical support (ie. answers to “how do I make the type system do this?” questions) if anyone else wants to take on the job, though. (the type-transformers above should be enough to get started)

0reactions

leeoniyacommented, Oct 8, 2021

before committing to this route, i’d like to see an initial scaffold PR for what this might look like; don’t bother doing the entire typings file, but a decent amount of it that covers different cases, including multi-level nested computed types. if it looks reasonable enough to maintain, then we can go ahead.