Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Usage Issues] No TODOs found in repo with lots of TODO #6

Open
Olshansk opened this issue Jan 28, 2025 · 5 comments
Open

[Usage Issues] No TODOs found in repo with lots of TODO #6

Olshansk opened this issue Jan 28, 2025 · 5 comments

Comments

@Olshansk
Copy link

tl;dr @azat-io Can you help us run this for poktroll?


This is a follow-on from #5.

Firstly, thank you for fixing it!

I'd love to give this tool a shot but still hitting some issues and can't (choosing not to) commit the time to really diving in to debug in detail.

  • Goal: I'm interested in tracking the evolution / changes in TODOs in poktroll:

    git [email protected]:pokt-network/poktroll.git`
    
  • Quick validation: If you search for TODO in the repo (see search link). Screenshot for reference:
    Image

  • What I did: Run npx todoctor from the root directory of ☝. Results:
    Image

  • Intuition: Might be related to how the TODO regexes are identified in identify_todo_comment or just miscellaneous issue (dependencies, path, etc)

@Olshansk Olshansk changed the title [Usage Issues] No TODOs found [Usage Issues] No TODOs found in repo with lots of TODO Jan 28, 2025
@moltar
Copy link

moltar commented Jan 28, 2025

In the docs it state that it works with JS/TypeScript only.

@Olshansk
Copy link
Author

@moltar @azat-io sorry for missing that!

Would either of you potentially have time to look into adding Go and python as well?

@moltar
Copy link

moltar commented Jan 28, 2025

Definitely not me! 😁 I'm just a happy todoctor user & don't know Rust nor Go.

@azat-io
Copy link
Owner

azat-io commented Jan 29, 2025

Hello. I'm sorry, but we have no plans to support Go or Python at this time.

@Olshansk
Copy link
Author

No worries!

I figure the high-level approach is:

  1. Iterate through git history 1 by 1
  2. grep for TODO in the codebase
  3. Track count
  4. Plot results

I think I can get Claude to generate a script (e.g. in Python) that'll be language agnostic.

Will follow up once I get it done and can potentially contribute to this repo 🫡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants