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.

Sign up for GitHub

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

Jump to bottom

be explicit about legal paths #13

Open
jbclements opened this issue Jul 12, 2016 · 2 comments
Open

be explicit about legal paths #13

jbclements opened this issue Jul 12, 2016 · 2 comments
Assignees
@jbclements

Comments

@jbclements
Copy link
Owner

state somewhere what the legal URL patterns are, and check them up front rather than allowing 'last' to fail somewhere deep within a sub-function.
@jbclements jbclements self-assigned this Jul 13, 2016
@jbclements
Copy link
Owner Author

with url.rkt, I think we're close on this. There's a single point of control... now we just have to wire everything up to it.

@jbclements jbclements mentioned this issue Aug 12, 2016
Open
@jbclements jbclements mentioned this issue Aug 31, 2016
Closed
@jbclements
Copy link
Owner Author

FWIW, url.rkt is now called paths.rkt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbclements jbclements

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jbclements