Use type hinting

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

No files, tests, or entry points are named. Review the repository's functions and identify those lacking return type hints; done means the functions have return annotations so editors and analyzers can inspect their return types.

Written by the indexing model from the issue text.

Description

documentation

Most functions currently do not return a type hint. By using this language feature it is easier for developers and intelligent code editors to analyze the code.

Dominant language
Python
Stars
763
Forks
126
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 mandiant/stringsifter

All issues in mandiant/stringsifter

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.