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

Optional parameters result in empty strings? #381

Open
vpzomtrrfrt opened this issue Sep 22, 2020 · 0 comments · May be fixed by #382
Open

Optional parameters result in empty strings? #381

vpzomtrrfrt opened this issue Sep 22, 2020 · 0 comments · May be fixed by #382

Comments

@vpzomtrrfrt
Copy link
Contributor

It appears that optional parameters are passed to the component as empty strings. I would have expected undefined instead.

If this is intentional, it should be documented
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proposal: unmatched optional path segments produce undefined prop values preactjs/preact-router
1 participant
@vpzomtrrfrt