Route with Paths vs Fragment

[GuilhermeMota93]

Had a need recently to support something else than Paths - so I stumbled upon the Fragment approach and thought I'd share

enum Route {
    case pages(pageId: String, subsectionId: String?)
    case deepPage(id: String, tab: String?)
}

let appRouter = OneOf {
    
    // GET /pages/:pageId
    // GET /pages/:pageId#subsectionId <------ this is a Fragment
    Route(.case(Route.pages)) {
        Path { "pages"; Parse(.string) }
        
        //for optionals in fragment
        AnyParserPrinter<URLRequestData, String?> { requestData in
            ((requestData.fragment?.isEmpty) == nil) ? nil : String(requestData.fragment ?? "") // fragment here
        } print: { output, input in
            if let output = output {
                input.path.prepend(output[...])
            }
        }
    }

    // GET /deepPage/:id
    // GET /deepPage/:id/:tab <------ this is a Path
    Route(.case(Route.deepPage)) {
        Path { "deepPage"; Parse(.string) }
        
         //for optionals in path
        AnyParserPrinter<URLRequestData, String?> { requestData in
            requestData.path.isEmpty ? nil : String(requestData.path.removeFirst()) // path here
        } print: { output, input in
            if let output = output {
                input.path.prepend(output[...])
            }
        }
    }
}

[kamcma]

The library ships with a fragment parser.

import URLRouting

enum FooRoute {
  case pages(id: String, subsection: String?)
  case deepPage(id: String, tab: String?)
}

struct FooRouter: ParserPrinter {
  var body: some Router<FooRoute> {
    OneOf {
      Route(.case(FooRoute.pages)) {
        Path { "pages"; Parse(.string) }
        Optionally {
          Fragment()
        }
      }
      Route(.case(FooRoute.deepPage)) {
        Path { "deepPage"; Parse(.string) }
        Optionally {
          Path { Parse(.string) }
        }
      }
    }
  }
}