Renamed "ticktick_todo" to "ticktick"

[Hantick]

Proposed change

TickTick has become a bigger software than just a todo list, it offers calendar, kanban planning and many more and I think that ticktick_todo name for that brand is invalid, in my opinion it should be named as ticktick as this is the official name of the brand and that one should be followed.

Type of change

• Add a new logo or icon for a new core integration
• Add a missing icon or logo for an existing core integration
• Add a new logo or icon for a custom integration (custom component)
  • I've added a link to my custom integration repository in the PR description
  • I've opened up a PR for my custom integration on the Home Assistant
    Python wheels repository
• Replace an existing icon or logo with a higher quality version
• Replace an existing icon or logo after a branding change
• Removing an icon or logo

Additional information

• This PR fixes or closes issue: fixes #
• Link to code base pull request:
• Link to documentation pull request:
• Link to integration documentation on our website:
• Link to custom integration repository:

Checklist

• The added/replaced image(s) are PNG
• Icon image size is 256x256px (icon.png)
• hDPI icon image size is 512x512px for ([email protected])
• Logo image size has min 128px, but max 256px, on the shortest side (logo.png)
• hDPI logo image size has min 256px, but max 512px, on the shortest side ([email protected])

[frenck]

This will collide in domain name with the core integration that is currently in the process of being added here:

home-assistant/core#118871

../Frenck

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Hantick]

This will collide in domain name with the core integration that is currently in the process of being added here:

home-assistant/core#118871

../Frenck

I'll contact with @arne182

[Hantick]

@frenck Arne closed his PR, I would like to create this integration as a custom one and later on after some testing and polishing the integration to the bugless state I would create the PR against the core

[frenck]

If that is the intention, I would still advise against the domain change, as you are now planning towards a future domain collision.

../Frenck

[Hantick]

@frenck I understand it, I will change the domain to ticktick_todo and post it to the HACS official repository, later on I will add tests and make integration bulletproof and eventually will post it as ticktick to the Core. Does that makes sense or I'm missing something?