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

Remove customize UI #10632

Merged
merged 3 commits into from Nov 17, 2021
Merged

Remove customize UI #10632

merged 3 commits into from Nov 17, 2021

Conversation

ludeeus
Copy link
Member

@ludeeus ludeeus commented Nov 17, 2021

Breaking change

Proposed change

This PR removes the "customize" UI, this is outdated and should not be used by anyone.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

@balloob balloob merged commit 1e851e0 into dev Nov 17, 2021
@balloob balloob deleted the Remove-customize-UI branch November 17, 2021 18:34
@balloob
Copy link
Member

balloob commented Nov 17, 2021

For context: customization dashboard writes to a YAML file that can be included in your configuration under the customize section, which needs to be manually set up. This option is sending users in the wrong direction as the correct place to customize entities is via the entities page.

You can still use the VSCode editor to edit customize

@home-assistant home-assistant locked as resolved and limited conversation to collaborators Nov 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants