-
Notifications
You must be signed in to change notification settings - Fork 27
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignoring path components #81
Comments
I am also having this issue. Did you manage to get this working in the end? |
Unfortunately not with the given Parsers.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone 馃憢
We are currently using URLRouting in our Application.
In our current case we've been facing a problem with the parsing of the path of an URL.
Use case:
The link which will be parsed looks like this:
https://example.de/colors
In some cases this link can have multiple path components. The number of path components is not fixed and we do not know how many additional path components are added to this link (0..n).
Is there any way this can be done. We tried multiple combinations with Skip, Many and Rest but the problem seems to be that the Path component passes one element to the Parser at a time.
The workaround for us would be to implement a custom Path parser which does not pass the path components one by one but the whole path at once. So we can work with the Prefix Parser.
We'd like to know if there is a better way with the given component?
Thank you for having a look at this. 馃憤
Following a code example to represent the problem.
The text was updated successfully, but these errors were encountered: