Ideas for further checks about loguru-mypy HOT 6 OPEN

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.82. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

from loguru-mypy.

@Delgan if you have something more feel free to let me know :). If there are some users already, let us know too :)

from loguru-mypy.

There are different possible errors "at runtime", I guess we can figure out some of them by looking at the raise statements in the loguru sources.

Here are some examples of code causing exceptions but not detected by mypy / type-hints:

• logger.add(sys.stderr, level=-10) (negative level not allowed)
• logger.level("FOOBAR", no=-10) (negative level not allowed)
• logger.log(-10, "Message") (negative level not allowed)
• logger.level("INFO", no=111) (updating the no of an existing level is not allowed)
• logger.add("file.txt", foobar="xyz") (the open() builtin does not have a foobar argument)

There is also a whole range of "parsing" issues that I didn't listed (like parsing of color tags or rotation/retention).

from loguru-mypy.

Hmm...I think we can take some od those for later. @Delgan if you want to dive into wonderful world od mypy feel free to implement either of those 😁

from loguru-mypy.

Honestly, I don't think it's worth spending time implementing this. I was just throwing some ideas. 😁

from loguru-mypy.

well perhaps having levels defined as int is enough. This is how typeshed does that. Maybe colors could be done like so if for example you requre hex like color codes, we could check against that. But that might low on prio for us.
I will keep this one here. If we people start using this plugin, they will be the best judge we can get ;)

from loguru-mypy.