Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify documentation for Servant.Links.allLinks #1751

Open
danidiaz opened this issue May 8, 2024 · 0 comments
Open

Clarify documentation for Servant.Links.allLinks #1751

danidiaz opened this issue May 8, 2024 · 0 comments

Comments

@danidiaz
Copy link

danidiaz commented May 8, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant