-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Reuse last resource from url dispatch table #2586
Comments
I'm working on it |
Hmm it's not allowed to add a route with existing path and name as it's already handled by
See below
Should I match only the path ? |
The feature should check both |
Ok got it, pull request soon |
Do not create a new resource when adding a route with the same name and path of an existing resource
Do not create a new resource when adding a route with the same name and path of an existing resource
Do not create a new resource when adding a route with the same name and path of the last added resource.
* Avoid to create unnecessary resources (#2586) Do not create a new resource when adding a route with the same name and path of the last added resource. * Add a test for AbstractResource().raw_match() * PrefixResource().raw_match() should always return False
Fixed by #2603 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
If name and path is the same -- add a route to existing resource instead of creating a new one.
E.g.
should create the single resource if path and name are the same.
It reduces resources table size and boosts url lookup if handlers for the same url is grouped together.
The change is easy, Pull Request is welcome.
The text was updated successfully, but these errors were encountered: