propensive/serpentine

Issues

• Improve representation of valid/invalid path characters

  #20 opened 6 months ago by propensive
  0

• Links should be a general type parameterized on path type

  #19 opened 9 months ago by propensive
  0

• Allow pattern matching on paths

  #18 opened a year ago by propensive
  2

• Reduce number of type parameters in `Hierarchy`

  #10 opened a year ago by propensive
  0

• Try to avoid name conflict with `gossamer.text`

  #11 opened a year ago by propensive
  0

• Use `Hierarchy` to provide `/` method on a `Root`

  #12 opened a year ago by propensive
  1

• Provide combined absolute/relative `parse` method on `Hierarchy`

  #13 opened a year ago by propensive
  0

• Support absolute/relative paths which can't be parsed

  #14 opened a year ago by propensive
  0

• Provide `Show` instances

  #15 opened a year ago by propensive
  0

• Split reading and construction of `Path`s and `Link`s into two typeclasses

  #16 opened a year ago by propensive
  0

• Use a typeclass for the parameter to `/` in paths

  #17 opened a year ago by propensive
  0

• Encode case (in)sensitivity in paths

  #9 opened a year ago by propensive
  0

• Add more tests

  #4 opened a year ago by propensive
  0

• Parsing relative path includes spurious empty string

  #5 opened 2 years ago by propensive
  0

• Change interface from inheritance to typeclass-based

  #6 opened a year ago by propensive
  0

• Create a string interpolator for paths

  #7 opened 2 years ago by propensive
  0

• Constrain path characters in Relative

  #8 opened a year ago by propensive
  0

• Experiment with encoding the depth of the path in its type

  #1 opened 2 years ago by propensive
  1