Skip to content

Add logging for a better dev experience #12

Open
@Sharp-Eyes

Description

@Sharp-Eyes

Summary

Add logging to e.g. custom_id creation such that it is easier for people to figure out if something went wrong and why.

What is the feature request for?

disnake.ext.components

The Problem

Currently, just about everything the module does, happens internally, away from the user's influence except for any exceptions that are raised. Providing logging for some internal actions that are taken would make it easier to debug any issues. This holds both for fixing bugs with the library, and for the end-developer to more quickly figure out if something went wrong due to an error they made in setting up the component listeners.

The Ideal Solution

Add logging debug logging to a couple parts of the internals. Ideally use different loggers so users can pick which they want to enable/disable. of

The Current Solution

There currently is no solution to this problem, outside of writing custom listener classes, which is not really feasible.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttarget: rewriteThis will be completed in the rewrite.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions