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

Switch to log/slog #549

Closed
1 of 2 tasks
jkroepke opened this issue Feb 24, 2024 · 2 comments · Fixed by #557
Closed
1 of 2 tasks

Switch to log/slog #549

jkroepke opened this issue Feb 24, 2024 · 2 comments · Fixed by #557

Comments

@jkroepke
Copy link
Contributor

Preflight Checklist

  • I could not find a solution in the existing issues, docs, nor discussions
  • I have joined the ZITADEL chat

Describe your problem

While log/slog and golang.org/x/exp/slog having the same API, they could not used together.

According to the README, if zitadel/oidc switches to go 1.22, it should be safe to use log/slog, since it's supported since go 1.21.

Describe your ideal solution

I'm able to pass the log/slog logger to zitadel/oidc library calls.

Version

3.12.0

Environment

Self-hosted

Additional Context

No response

@muhlemmer
Copy link
Collaborator

I had some issues installing go 1.22 on my system, but managed Friday. I will do the version bumping stuff after the weekend, along with the move to log/slog

Copy link

🎉 This issue has been resolved in version 3.13.0 🎉

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants