Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WECHATY_LOG environment variable specification (valid values) #2167

Closed
huan opened this issue Apr 4, 2021 · 1 comment
Closed

WECHATY_LOG environment variable specification (valid values) #2167

huan opened this issue Apr 4, 2021 · 1 comment

Comments

@huan
Copy link
Member

huan commented Apr 4, 2021

According to our Wechaty Specification https://wechaty.js.org/docs/specs/wechaty:

The WECHATY_LOG should support the values of silly, verbose, info, warn, silent

All Polyglot Wechaty should at least support the above names as an alias.

Copy link

dosubot bot commented Nov 16, 2023

Hi, @huan. I'm Dosu, and I'm helping the wechaty team manage their backlog. I wanted to let you know that we are marking this issue as stale.

From what I understand, you opened this issue to propose defining the valid values for the WECHATY_LOG environment variable in the Wechaty Specification. You suggested that all Polyglot Wechaty should support the aliases silly, verbose, info, warn, and silent. However, there hasn't been any activity or comments on the issue since you opened it.

Before we close this issue, we wanted to check with you if it is still relevant to the latest version of the wechaty repository. If it is, please let us know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days.

Thank you for your contribution, and we appreciate your understanding. Let us know if you have any further questions or concerns.

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 16, 2023
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 23, 2023
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant