[snfx-johaver]

I'd like to add two writable properties to the To Do SDK:

task.importance = 'low'  # 'low', 'normal', or 'high'; also accepts ImportanceLevel members
task.save()

checklist_item.displayname = 'Review the contract'
checklist_item.save()

Both use the existing change tracking. The importance setter uses the shared ImportanceLevel enum and its string conversion, while keeping the existing string getter compatible. Invalid values raise ValueError, and unrelated saves don't send or reset importance. Renaming a checklist item doesn't change its checked state.

I've added usage examples and 34 passing request-level regression tests covering string and enum inputs, creates, updates, validation, combined edits, preservation, and retry after a failed save. Run with PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest tests/test_tasks.py -q (plugin autoload is disabled to avoid an unrelated locally installed Home Assistant plugin).

This unblocks RogerSelwyn/MS365-ToDo#199 once these SDK changes are merged and released. I haven't changed the package version or assumed a release number.

[RogerSelwyn]

I think this should be using an eNum for enforcing the value, there is an example in Calendar Event.

from .utils import ImportanceLevel

    @importance.setter
    def importance(self, value):
        self.__importance = (value if isinstance(value, ImportanceLevel)
                             else ImportanceLevel.from_value(value))
        self._track_changes.add(self._cc('importance'))

Imo

[snfx-johaver]

Thanks, Roger — updated to use the shared ImportanceLevel enum and its string conversion. It now accepts enum members too, while keeping the existing string getter compatible. Invalid values still raise ValueError. All 34 tests pass, including string and enum inputs for each importance level.

_{Auto-replied by the GitHub Copilot app}