Skip to content

Conversation

shreykumar18
Copy link

@shreykumar18 shreykumar18 commented Mar 9, 2023

Description

What is changing?

Instead of a "[object Object] can only have authSource set to '$external'", where obviously "[object Object]" error message, when a connection string is provided, the object is now clarified.

Is there new documentation needed for these changes?

No new documentation needed.

What is the motivation for this change?

It was a bug, that provided an unclear error message. The expected behaviour was to specify the object of the connection string when the authSource isn't set to $external.

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@dariakp dariakp changed the title fix[NODE 4518]!: Bug Fix - Unclear Error Message AuthSource isn't set to $external. fix(NODE 4518)!: Bug Fix - Unclear Error Message AuthSource isn't set to $external. Mar 9, 2023
@dariakp dariakp added tracked-in-jira Ticket filed in MongoDB's Jira system External Submission PR submitted from outside the team labels Mar 9, 2023
@baileympearson
Copy link
Contributor

Hey @shreykumar18 - thanks for bringing our attention to this bug again. We decided to go with a slightly different approach, implemented here. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
External Submission PR submitted from outside the team tracked-in-jira Ticket filed in MongoDB's Jira system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants