specCon18/YUNODO
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
This repository has been archived on 2025-06-21. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.
15 commits 1 branch 0 tags 60 KiB
Find a file
Jeremiah S f7653a4a5d
added checks to prevent bad pushes
2024-05-31 12:24:21 -04:00
.direnv implemented basic data extraction 2024-05-30 20:54:36 -04:00
.github/workflows added checks to prevent bad pushes 2024-05-31 12:24:21 -04:00
nix implemented basic data extraction 2024-05-30 20:54:36 -04:00
src added format match statement 2024-05-30 20:54:36 -04:00
.envrc implemented basic data extraction 2024-05-30 20:54:36 -04:00
.gitignore implemented basic data extraction 2024-05-30 20:54:36 -04:00
Cargo.lock added toml support 2024-05-30 20:54:36 -04:00
Cargo.toml added toml support 2024-05-30 20:54:36 -04:00
flake.lock implemented basic data extraction 2024-05-30 20:54:36 -04:00
flake.nix implemented basic data extraction 2024-05-30 20:54:36 -04:00
LICENSE Initial commit 2024-05-30 20:51:29 -04:00
LICENSE.md added license 2024-05-30 20:54:36 -04:00
README.md Update README.md 2024-05-30 20:56:32 -04:00

README.md

YUNODO(Why you no do?)

I needed a tool to find all of my "//TODO:"s in my code so I wrote this.

Q&A

Q:is it over engineered? A:yes. yes it is.

Q:do I care that it's over engineered? A:no. no I don't.

Q:should you have that it's over engineered? A:no if you don't like it gon' now git!

Purpose

take comments like the following and output them in a parser/reader friendly format.

Input:

//TODO:this is a todo comment:ODOT//

Output:

File Path File Name Line Number Comment
./src/ README.md 17 this is a todo comment