chase-moskal/renraku

Issues

• todo

  #22 opened 5 months ago by chase-moskal
  0

• complete the readme documentation

  #11 opened 5 months ago by chase-moskal
  0

• browser automated tests

  #14 opened 5 months ago by chase-moskal
  1

• better test coverage

  #15 opened 5 months ago by chase-moskal
  1

• full json-rpc spec compliance

  #16 opened 5 months ago by chase-moskal
  1

• Read me docs when??

  #21 opened 2 years ago by xXWarMachineRoXx
  1

• socket error handling should be improved

  #9 opened 3 years ago by chase-moskal
  0

• allow the "authorization" header in allow-cors

  #13 opened 3 years ago by chase-moskal
  0

• web sockets need a mechanism to keep alive

  #17 opened 3 years ago by chase-moskal
  1

• fix readme: wrong imports (forgot /x/)

  #18 opened 3 years ago by chase-moskal
  0

• nested services are not working

  #19 opened 3 years ago by chase-moskal
  0

• fix build

  #20 opened 3 years ago by chase-moskal
  0

• ci/cd: github actions for builds on master, and npm deployment on tags

  #10 opened 3 years ago by chase-moskal
  1

• logging

  #12 opened 3 years ago by chase-moskal
  0

• rewrite renraku

  #8 opened 3 years ago by chase-moskal
  1

• rate limiting design and implementation

  #7 opened 3 years ago by chase-moskal
  0

• rework readme

  #6 opened 3 years ago by chase-moskal
  0

• remove the extra policy.processAuth and make 'policy' the function

  #5 opened 3 years ago by chase-moskal
  2

• json-rpc spec compliance

  #4 opened 4 years ago by chase-moskal
  2

• make room for options like 'debug' in create-api-server

  #3 opened 6 years ago by chase-moskal
  1

• to merge or not to merge? with crosscall?

  #1 opened 6 years ago by chase-moskal
  1

• refactor callee/callable topics structure

  #2 opened 6 years ago by chase-moskal
  0