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

Follow up on Wildcard support #308

Closed
muhlemmer opened this issue Mar 6, 2023 · 2 comments · Fixed by #328
Closed

Follow up on Wildcard support #308

muhlemmer opened this issue Mar 6, 2023 · 2 comments · Fixed by #328
Assignees
@muhlemmer
Labels
released on @next released

Comments

@muhlemmer
Copy link
Collaborator

This is a follow issue on, #297 which was a quick-fix for #293 on main. However, I would like to see if we can implement path.Match without an API and storage change. It would keep usage more simple for the end-user if we can use the same fields for URL input.

I will investigate later this week and come with a proposal.
@muhlemmer muhlemmer self-assigned this Mar 6, 2023
@muhlemmer muhlemmer added this to the v2 milestone Mar 6, 2023
@muhlemmer muhlemmer removed this from the v2 milestone Mar 15, 2023
@muhlemmer muhlemmer mentioned this issue Mar 17, 2023
Merged
@muhlemmer muhlemmer moved this to 👀 In review in Product Management Mar 17, 2023
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Product Management Mar 28, 2023
@github-actions
Copy link

🎉 This issue has been resolved in version 2.2.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented May 2, 2023

🎉 This issue has been resolved in version 3.0.0-next.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@muhlemmer muhlemmer

Labels
released on @next released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: document non-standard glob client zitadel/oidc
1 participant
@muhlemmer