The haddocks for allLinks have the following note:
nested APIs don't work well with this approach
and an example is given.
Does that mean that for nested APIs the links aren't correctly generated, or simply that the resulting "link builder" values like Char -> (Int -> Link) :<|> (Double -> Link) are unwieldly to use?
In the second case, perhaps it should be mentioned that allLinks still works when the nested APIs are represented with route records (video example here) and the ergonomics are better with records. Perhaps a doctest example could be given.
The haddocks for
allLinkshave the following note:and an example is given.
Does that mean that for nested APIs the links aren't correctly generated, or simply that the resulting "link builder" values like
Char -> (Int -> Link) :<|> (Double -> Link)are unwieldly to use?In the second case, perhaps it should be mentioned that
allLinksstill works when the nested APIs are represented with route records (video example here) and the ergonomics are better with records. Perhaps a doctest example could be given.