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

Encode routed resources in the Conn type #2

Closed
owickstrom opened this issue Dec 10, 2016 · 1 comment
Closed

Encode routed resources in the Conn type #2

owickstrom opened this issue Dec 10, 2016 · 1 comment

Comments

@owickstrom
Copy link
Collaborator

As described in https://owickstrom.github.io/hyper/#resource-routers, routed resources are not part of the Conn type. They should be encoded as a component in the Conn, if possible. My hope is that a resource A referencing another resource B, can do so through the conn, making dependencies explicit:

\conn -> html (linkTo conn.components.routes.home (text "Home Page") conn)

I think this would also result in less need for explicit type annotations when having mutually referencing resources.

@owickstrom
Copy link
Collaborator Author

Closing this in favor of new router work.

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

No branches or pull requests

1 participant