Skip to content

Fix module names for custom components#14317

Merged
balloob merged 4 commits intodevfrom
fix-custom-component-name
May 7, 2018
Merged

Fix module names for custom components#14317
balloob merged 4 commits intodevfrom
fix-custom-component-name

Conversation

@balloob
Copy link
Copy Markdown
Member

@balloob balloob commented May 6, 2018

Description:

After #14211, the __name__ attribute on custom components no longer had the custom_component prefix. This fixes it.

Related issue (if applicable): fixes #14304

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

@balloob balloob added this to the 0.69 milestone May 6, 2018
@balloob balloob requested a review from a team as a code owner May 6, 2018 17:09
@homeassistant homeassistant added cla-signed core small-pr PRs with less than 30 lines. labels May 6, 2018
@balloob balloob merged commit 34727be into dev May 7, 2018
@balloob balloob deleted the fix-custom-component-name branch May 7, 2018 02:01
@balloob
Copy link
Copy Markdown
Member Author

balloob commented May 7, 2018

This doesn't fix it :( Loggers initialize themselves when the module is executed, updating it afterwards is too late.

balloob added a commit that referenced this pull request May 7, 2018
* Fix module names for custom components

* Also set __package__ correctly

* bla

* Remove print
@balloob balloob mentioned this pull request May 11, 2018
@home-assistant home-assistant locked and limited conversation to collaborators Sep 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Custom_components in 0.69

3 participants