[amix]

Context

• Table becomes a regular project view style in the API, like list, board and calendar (Doist/Todoist#31065).

What was changed

• add_project / update_project accept view_style="table", and ViewStyle includes it.
• Docstrings list all four view styles.
• test_add_project_full covers table as well as board.

Refs

• Merge after Doist/Todoist#31065 is deployed. fix: load projects with unknown view styles #269 separately keeps loading projects whose view style the SDK doesn't know.

🤖 Generated with Claude Code

[doistbot]

This PR cleanly adds table as a fourth project view style, updating the ViewStyle definitions, the add_project/update_project docstrings, and extending the parametrized test coverage for both sync and async clients. No inline issues were flagged. One minor note: the allowed values now live as two parallel ViewStyle definitions that must be kept in sync manually — worth keeping an eye on as view styles evolve, though unifying them may be out of scope here.

I also included a few optional follow-up notes in the details below.

Optional follow-up notes (2)

• todoist_api_python/types.py:38: The allowed values are duplicated here and in models.py's ViewStyle Literal, so every new view style (like this PR's "table") must be added in both places. To keep a single source of truth, types.py could reuse the Literal, e.g. Predicate(lambda value: value in get_args(models.ViewStyle)), or the Literal could be defined here and re-exported by models.py.
• tests/test_api_projects.py:163: test_add_project_full now covers table for add_project, but the same PR also adds table to update_project and no test passes view_style through that path (test_update_project's args omit it). Add view_style: "table" to test_update_project's request/response args, or parameterize that test as well, so the update passthrough is protected.

_{Share Feedback • Review Logs}