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

Refactor todo services and their schema #103079

Merged
merged 2 commits into from Oct 30, 2023
Merged

Refactor todo services and their schema #103079

merged 2 commits into from Oct 30, 2023

Conversation

edenhaus
Copy link
Contributor

@edenhaus edenhaus commented Oct 30, 2023

Breaking change

Proposed change

As discussed today to improve the user experience:

  • Rename "Summary" ➝ "Item name" (make it item in the parameter)
  • "Create to-do list item" ➝ "Add a to-do list item" ➝ including the todo.create_item ➝ todo.add_item service handle.
  • "Delete to-do list item" ➝ "Remove a to-do list item" ➝ including the todo.delete_item ➝ todo.remove_item service handle.
  • For create a new to-do list item, remove the status, and use "needs action" by default.
  • Squash unique ID & summary field into item.

Type of change

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

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

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

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (todo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of todo can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign todo Removes the current integration label and assignees on the pull request, add the integration domain after the command.

@bramkragten
Copy link
Member

Will work on adapting the frontend to changed services

@bramkragten
Copy link
Member

home-assistant/frontend#18477

@bramkragten bramkragten merged commit d97a030 into dev Oct 30, 2023
23 checks passed
@bramkragten bramkragten deleted the edenhaus-rename-todo branch October 30, 2023 20:43
@github-actions github-actions bot locked and limited conversation to collaborators Nov 1, 2023
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

4 participants