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

feat(router): adapt to new hash table implementation #33

Merged
merged 3 commits into from
Feb 12, 2022

Conversation

jfontan
Copy link
Contributor

@jfontan jfontan commented Feb 12, 2022

No description provided.

apoorvcodes and others added 3 commits February 12, 2022 10:19
@apoorvcodes
Copy link
Member

#30 Ig we can work on this issue now

Copy link
Member

@apoorvcodes apoorvcodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me!

@megatank58 megatank58 changed the title New router feat(router): adapt to new hash table implementation Feb 12, 2022
@megatank58 megatank58 merged commit e9683e4 into gominima:hash-table Feb 12, 2022
@apoorvcodes apoorvcodes linked an issue Feb 13, 2022 that may be closed by this pull request
megatank58 pushed a commit that referenced this pull request Feb 15, 2022
* feat(router): adapt to new hash table implementation (#33)

* New router implementation

It is still not linked to the proper router implementation

* Swap mux implementation to use new routes

Co-authored-by: Apoorv <tofu.develops@gmail.com>

* feat: UseRouter with new router implementation

* feat: Mount with new router implementation

* feat: custom notfound handler

* chore: remove useless code

* feat: documentation for mux

* fix: bug in route matching

* chore: remove useless code

* feature: support /path/:var/fixed/:var2 paths

Previously matching fixed parts after a variable was not supported.

Note: When two routes can match the same path the first one will be
used. For example, if these two routes are registered:

* `/path/:var/:var3/:var2`
* `/path/:var/fixed/:var2`

The path `/path/one/fixed/two` will match the first route.

* chore: mux documentation

* chore: remove query param from readme

* chore: documentation cleanup

Co-authored-by: Javi Fontan <jfontan@gmail.com>
Co-authored-by: ToTu-Dev <75479355+ToTu-Dev@users.noreply.github.com>
megatank58 pushed a commit that referenced this pull request Feb 16, 2022
* feat(router): adapt to new hash table implementation (#33)

* New router implementation

It is still not linked to the proper router implementation

* Swap mux implementation to use new routes

Co-authored-by: Apoorv <tofu.develops@gmail.com>

* feat: UseRouter with new router implementation

* feat: Mount with new router implementation

* feat: custom notfound handler

* chore: remove useless code

* feat: documentation for mux

* fix: bug in route matching

* chore: remove useless code

* feature: support /path/:var/fixed/:var2 paths

Previously matching fixed parts after a variable was not supported.

Note: When two routes can match the same path the first one will be
used. For example, if these two routes are registered:

* `/path/:var/:var3/:var2`
* `/path/:var/fixed/:var2`

The path `/path/one/fixed/two` will match the first route.

* chore: mux documentation

* chore: remove query param from readme

* chore: documentation cleanup

* feat: query can be donated with ?q in path

* feat: no need of rawhandler

* chore: readme fix

* feat: added makefile

* chore: remove duplicate methods

* chore: no more query params

* chore: fix review issues

Co-authored-by: Javi Fontan <jfontan@gmail.com>
Co-authored-by: ToTu-Dev <75479355+ToTu-Dev@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

[Examples]: Write examples for the docs
3 participants