Skip to content

Conversation

grdsdev
Copy link
Contributor

@grdsdev grdsdev commented Jul 29, 2025

What kind of change does this PR introduce?

Improvement

What is the current behavior?

User needs to manually implement a SupabaseLogger which uses a OSLog.

What is the new behavior?

We now provide a SupabaseLogger implementation that uses OSLog, since this is probably the most used logger across Apple projects.

@coveralls
Copy link

coveralls commented Jul 29, 2025

Pull Request Test Coverage Report for Build 16607682663

Details

  • 0 of 18 (0.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.2%) to 78.056%

Changes Missing Coverage Covered Lines Changed/Added Lines %
Sources/Helpers/Logger/OSLogSupabaseLogger.swift 0 18 0.0%
Totals Coverage Status
Change from base Build 16605636117: -0.2%
Covered Lines: 5485
Relevant Lines: 7027

💛 - Coveralls

@grdsdev grdsdev merged commit c067c52 into main Jul 30, 2025
16 of 17 checks passed
@grdsdev grdsdev deleted the guilherme/create-os-log-supabase-logger branch July 30, 2025 08:15
@supabase-releaser
Copy link

🎉 This PR is included in version 2.31.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@arbyruns
Copy link

Just learning about this. Is there an advantage of using this over implementing logger yourself?

@grdsdev
Copy link
Contributor Author

grdsdev commented Aug 25, 2025

@arbyruns this is only a convenience logger implementation, if you use OSLog as the logger backend, then it makes sense to use this instead of reimplementing your own.

If you use a different logging backend, then you implement your own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants