Skip to content

Issues: sebinsua/ramda-debug

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.

Sign up for GitHub

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

8 Open 3 Closed
8 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider use of R.tap inwards and outwards.
#12 opened Jul 20, 2015 by sebinsua
2
#idea Implement a small educational console/repl library on top of this.
#10 opened May 19, 2015 by sebinsua
3
Separate formatting and logging from data collection (partially through use of emit/flush.)
#8 opened May 17, 2015 by sebinsua
@sebinsua
1
Separate logging of calls, returns and errors.
#7 opened May 17, 2015 by sebinsua
@sebinsua
Restructure codebase, add linting in and write unit tests.
#6 opened May 17, 2015 by sebinsua
@sebinsua
1
Avoid printing out multiple executions. By default print a sample: [0, 1, 2, ... N-1, N].
#5 opened May 17, 2015 by sebinsua
Make the execution signature concise for large arrays/objects.
#4 opened May 17, 2015 by sebinsua
Make it easy to choose which functions are logged and in what order.
#3 opened May 17, 2015 by sebinsua
ProTip! Find all open issues with in progress development work with linked:pr.