This repository was archived by the owner on Apr 29, 2022. It is now read-only.
Use Flask routing to allow for variables in URL #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is great, thanks @clarkduvall! I'm using your fork until this gets merged upstream. |
|
Going to go with #18 |
|
Works for me, thanks @kennethreitz! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows for variable URLs with no change to the current API.
I saw that there was already a pull request for this here: https://github.com/kennethreitz/flask-sockets/pull/7, but I think the solution proposed in this PR is cleaner, with no breaking changes. Based on the other pull request, it looks like a lot of people want this feature.
@kennethreitz what do you think?