Toodles scrapes your entire repository for TODO entries and organizes them so you can manage your project directly from the code. View, filter, sort, and edit your TODO's with an easy to use web application. When you make changes via toodles, the edits will be applied directly the TODO entries in your code. When you're done, commit and push your changes to share them with your team!
Specify details about your TODO's so that you can filter and sort them with
ease! Specify details within parenthesis and separate with the
p=<integer> will be interpreted as a priority number
Use arbitrary key value pairs
<key>=<value>|<key2>=<value2>|... and design any
organization scheme you wish! A good use for this is to enter dates of deadlines
for TODO's that you can sort on in Toodles
A detail starting with
#bug|#techdebt|#database|... will be interpreted as
a tag, which can be used to label and group your TODO's.
Assign your TODO's to someone. Any plain word that will be interpreted as an assignee.
# TODO(bob) - something we need to do later
Per Project Configuration
You can configure toodles by putting a
.toodles.yaml file in the root of your
project. See this repo's
.toodles.yaml for the full configuration spec.
Currently via config you can:
- Set files to ignore via a list of regular expressions
- Specify your own flags to scan for other than the built-ins (TODO, FIXME, XXX)
Ignore as many files as you can! Large autogenerated files will slow Toodles
down quite a bit. Check the output of the server to see any files/folders that
may be causing slowness for your repo and add them to the
ignore section your
.toodles.yaml If the performance of Toodles is not good enough for your use
case, please open an issue.
These languages will be scanned for any TODO's:
- Plaintext files (
- Shell / Bash
- Vue (scripts only)
Submit a PR if you'd like a language to be added. There will eventually be support for this to be user configurable
Installing with Scarf
Scarf is the easiest way to get Toodles.
$ scarf install toodles
Installing with Docker
You can run a pre-built toodles for your current directory via docker:
# execute toodles for the directory you are currently in: $ docker run -it -v $(pwd):/repo -p 9001:9001 aviaviavi/toodles
Just mount your project into the container's
/repo and direct a port of your
choice to the container's
Toodles builds with stack. Just a
build should do it. If you'd like to build toodles without cloning the source,
you can have stack build toodles with
stack install --resolver=lts-12.14 toodles!
Building with Docker
For convenience this repository also provides a
Dockerfile to automatically
# to build container run: $ cd /path/to/toodles/repo $ docker build -t toodles Dockerfile.dev . # afterwards you can run the following command to execute toodles for the # directory you are currently in: $ docker run -it -v $(pwd):/repo -p 9001:9001 toodles
toodles with no arguments will treat the current directory as the
project root and will start a server on port 9001. You can set these with the
-p flags, respectively.
# $ toodles -d <root directory of your project> -p <port to run server> # for more info run: # $ toodles --help $ toodles -d /path/to/your/project -p 9001 # or simply $ toodles
If Toodles is useful to you or your organization, please consider supporting the project by purchasing Toodles on Scarf.
Contributions in any form are welcome! A few bits of info:
- Don't be shy, ask questions! Contributing to Toodles should be welcoming for people at any level of programming familiarity. Whether it's a new feature, bug fix, or docs, any contribution is very appreciated.
- Open an issue or jump into the chat room on gitter
- Before you start coding, please comment or mark a particular issue as "in progress", or even open your pull request as a work in progress (WIP). This is to help avoid having multiple people work on the same thing.
- If github issues don't cut it, feel free to reach out on gitter or twitter @avi_press