-
Notifications
You must be signed in to change notification settings - Fork 8
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: supabase-community/supabase-ex
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.6.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: supabase-community/supabase-ex
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 12 commits
- 95 files changed
- 4 contributors
Commits on Feb 4, 2025
-
chore: solve on_response unatural return (#60)
## Problem N/A ## Solution fixes #59 ## Rationale N/A
Configuration menu - View commit details
-
Copy full SHA for 2454654 - Browse repository at this point
Copy the full SHA 2454654View commit details
Commits on Feb 7, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 16b1501 - Browse repository at this point
Copy the full SHA 16b1501View commit details
Commits on May 2, 2025
-
docs: update readme for version compatibility (#64)
## Problem The `~> 0.5` of the supabase-potion package caused version `0.6` to be pulled in. But `0.6` requires a major version upgrade of the postgrest package. ## Solution Update the docs to avoid version mismatches.
Configuration menu - View commit details
-
Copy full SHA for 614fc39 - Browse repository at this point
Copy the full SHA 614fc39View commit details
Commits on May 31, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 494e6c5 - Browse repository at this point
Copy the full SHA 494e6c5View commit details -
Configuration menu - View commit details
-
Copy full SHA for cd8138a - Browse repository at this point
Copy the full SHA cd8138aView commit details
Commits on Jun 26, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 523a225 - Browse repository at this point
Copy the full SHA 523a225View commit details
Commits on Jun 30, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c9d02fe - Browse repository at this point
Copy the full SHA c9d02feView commit details
Commits on Jul 20, 2025
-
Configuration menu - View commit details
-
Copy full SHA for e290e05 - Browse repository at this point
Copy the full SHA e290e05View commit details -
enable OTP email, add debug logs and enable realtime locally (#62)
## Problem The current version of `supabase-ex` lacks comprehensive logging capabilities, making it difficult for developers to debug issues when interacting with Supabase services. Additionally, the local development configuration needs updates to enable essential services like Realtime and Inbucket for testing. Documentation also requires updates to reflect new dependency versions and available integrations. ## Solution This PR implements several focused improvements: 1. Added proper logging throughout the Fetcher module using the standard Logger functionality 2. Updated the local Supabase configuration (`config.toml`) to enable Realtime, Inbucket, and appropriate authentication settings 3. Added email templates for various authentication flows 4. Updated dependency versions in documentation from `0.5` to `0.6` 5. Added references to Edge Functions and Realtime integrations in the README 6. Added a new section on debugging and logging configuration The changes ensure that error handling in the HTTP client provides appropriate log messages at debug and error levels, respecting the application's configured log level. ## Rationale These improvements address several practical needs: 1. **Enhanced Logging**: The strategic placement of log statements in error handling paths provides better visibility into request failures without being overly verbose. Using the standard Logger module ensures compatibility with existing logging backends and configuration. 2. **Development Configuration**: Enabling Realtime, Inbucket and authentication services in the local development environment makes it easier for contributors to test their changes comprehensively. 3. **Documentation Updates**: The README changes ensure users are aware of all available integrations and use the correct dependency versions. The implementation maintains backward compatibility while improving developer experience. The logging approach follows established Elixir conventions by using appropriate log levels (debug for general issues, error for exceptions) and provides context-rich messages that will help diagnose issues during development and in production.
Configuration menu - View commit details
-
Copy full SHA for 9c4af52 - Browse repository at this point
Copy the full SHA 9c4af52View commit details -
Configuration menu - View commit details
-
Copy full SHA for a91232b - Browse repository at this point
Copy the full SHA a91232bView commit details -
Configuration menu - View commit details
-
Copy full SHA for f2397f7 - Browse repository at this point
Copy the full SHA f2397f7View commit details
Commits on Jul 21, 2025
-
Configuration menu - View commit details
-
Copy full SHA for af9eec9 - Browse repository at this point
Copy the full SHA af9eec9View commit details
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.