Skip to content

Conversation

@Akalanka47000
Copy link
Member

No description provided.

@Akalanka47000 Akalanka47000 changed the title fix: connection string errors not returned properly to the caller Fixes issue of connection string errors not returned properly to the caller Dec 14, 2025
@codecov
Copy link

codecov bot commented Dec 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses an issue where connection string validation errors were not being properly returned to callers. The fix modifies the URI validation approach in the Connect function by explicitly calling Validate() on the client options after applying the URI, and changes the connection string parsing logic.

Key Changes:

  • Modified URI handling to prioritize URI from ClientOptions over the ConnectionOptions.URI field
  • Added explicit validation call using clientOpts.ApplyURI(opts.URI).Validate() wrapped in lo.Must0
  • Changed from connstring.ParseAndValidate to connstring.Parse with error handling modification

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Akalanka47000 Akalanka47000 merged commit ccee571 into main Dec 14, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants