Consider type checking

Open
#668 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by reading issue #649, then review the type-checking scope for tmuxp and the possibly affected libtmux library. The issue names no files, tests, or entry points, so first establish the project areas involved and agree on what type consistency should cover; completion criteria are not yet defined.

Written by the indexing model from the issue text.

Description

While investigating #649, I thought to myself that this kind of issue is quite hard to prevent without type checking, and upgrading libs can get quite time consuming or risky. Since click and many libraries are getting more involved in type checking, it becomes simpler et more valuable to check type consistency.

Since this might also involve type checking libtmux, that might be a lot of work

Dominant language
Python
Stars
4.6k
Forks
248
Avg merge
2h 13m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tmux-python/tmuxp

All issues in tmux-python/tmuxp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.