sebinsua/ramda-debug

Issues

• Consider use of R.tap inwards and outwards.

  #12 opened 9 years ago by sebinsua
  2

• ramda-debug on the browser

  #13 opened 9 years ago by lube
  4

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

  #10 opened 9 years ago by sebinsua
  3

• Turn on/off debugging

  #2 opened 9 years ago by ThomasCrevoisier
  6

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

  #8 opened 9 years ago by sebinsua
  1

• Restructure codebase, add linting in and write unit tests.

  #6 opened 9 years ago by sebinsua
  1

• Separate logging of calls, returns and errors.

  #7 opened 9 years ago by sebinsua
  0

• Improve the README.md

  #9 opened 9 years ago by sebinsua
  1

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

  #5 opened 9 years ago by sebinsua
  0

• Make the execution signature concise for large arrays/objects.

  #4 opened 9 years ago by sebinsua
  0

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

  #3 opened 9 years ago by sebinsua
  0