wtetzner/exploding-fish

Issues

• Why is it called exploding fish?

  #29 opened 4 years ago by nbaumanGR
  1

• normalize-path behaviour seams incorrect in this scenario

  #28 opened 4 years ago by KiliStrider
  1

• Host should be decoded?

  #27 opened 5 years ago by agriffis
  5

• Mixing param & param-raw has unexpected results

  #26 opened 6 years ago by ignorabilis
  2

• Setting scheme does not work as expected

  #25 opened 6 years ago by jstewart
  1

• Reflection warnings

  #23 opened 6 years ago by valerauko
  1

• Weird path handling

  #22 opened 6 years ago by valerauko
  2

• Creating Uri without setting authority leads to unexpected behavior

  #18 opened 6 years ago by mikehwang
  1

• Spec support

  #21 opened 6 years ago by valerauko
  5

• NumberFormatException from URLs with literal IPv6 addresses

  #19 opened 7 years ago by ljosa
  0

• URIs without protocols not parsing as expected

  #16 opened 9 years ago by neverfox
  2

• resolve-path with a URI that does not end with "/"

  #13 opened 11 years ago by odues
  3

• Query segments of uri's not handled correctly.

  #8 opened 11 years ago by shriphani
  4

• The param function does not seem to be working with relative URIs.

  #5 opened 12 years ago by roanosullivan
  3

• Naming feedback

  #1 opened 12 years ago by christianromney
  4

• uri fails on relative URL

  #4 opened 12 years ago by genovese
  3

• problems using exploding-fish

  #3 opened 12 years ago by rwillig
  1