Search results

Consider use of R.tap inwards and outwards.

Status: Open.

#12 In sebinsua/ramda-debug;

· sebinsua opened on Jul 20, 2015

#idea Implement a small educational console/repl library on top of this.

Status: Open.

#10 In sebinsua/ramda-debug;

· sebinsua opened on May 19, 2015

Separate formatting and logging from data collection (partially through use of emit/flush.)

Status: Open.

#8 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015

Separate logging of calls, returns and errors.

Status: Open.

#7 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015

Restructure codebase, add linting in and write unit tests.

Status: Open.

#6 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015

Avoid printing out multiple executions. By default print a sample: [0, 1, 2, ... N-1, N].

Status: Open.

#5 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015

Make the execution signature concise for large arrays/objects.

Status: Open.

#4 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015

Make it easy to choose which functions are logged and in what order.

Status: Open.

#3 In sebinsua/ramda-debug;

· sebinsua opened on May 17, 2015