Skip to content
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.

fix💥: make naff always use the correct logger #643

Merged
merged 2 commits into from
Sep 13, 2022

Conversation

Kigstn
Copy link
Member

@Kigstn Kigstn commented Sep 12, 2022

What type of pull request is this?

  • Non-breaking code change
  • Breaking code change
  • Documentation change/addition
  • Tests change

Description

Naff was not always using the correct logger. This was due to the logger being imported before the imported variable was changed on Client initialisation.

const.logger has been converted to a function which ensures the fetched object is the set one.

Technically breaking if anyone imported and used the logger

Changes

  • convert const.logger to a function

Checklist

  • I've formatted my code with Black
  • I've ensured my code works on Python 3.10.x
  • I've tested my code

@Kigstn Kigstn changed the title fix: make naff always use the correct logger fix💥: make naff always use the correct logger Sep 13, 2022
@silasary silasary changed the base branch from dev to 2.x September 13, 2022 13:59
@silasary silasary merged commit 2448b20 into NAFTeam:2.x Sep 13, 2022
LordOfPolls pushed a commit that referenced this pull request Sep 14, 2022
* fix: fix usage of hybrid cmds with no localized names (#639)

* fix: make naff always use the correct logger by converting const.logger into a function

Co-authored-by: Astrea <[email protected]>
silasary added a commit that referenced this pull request Sep 15, 2022
silasary added a commit that referenced this pull request Sep 15, 2022
Revert "fix💥: make naff always use the correct logger (#643)"

This reverts commit 2448b20.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants