f04c474fc4
## Description - This PR adds a check to throw a proper error if the default database name is empty and an invalid database name is provided in the authentication section for mongo db. - Added JUnit test cases for the same. one for an invalid db name and one for a valid db name (Both with empty default db name) - There is one more issue observed here which is not taken part in this ticket. When you try to save the mongo data source with the default database name and empty database name under auth section. Once you try to save the data source it will throw an internal server error. Created a ticket for the same: https://app.zenhub.com/workspaces/data-integration-pod-6322a759b3296d249ce5c4ed/issues/gh/appsmithorg/appsmith/21598 Fixes #12260 ## Type of change - Bug Fix(non-breaking change which adds functionality) ## How Has This Been Tested? - Manual - JUnit TC added ### **Checklist**: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag ### **QA activity:** - [ ] Test plan has been approved by relevant developers - [x] Test plan has been peer reviewed by QA - [ ] Cypress test cases have been added and approved by either SDET or manual QA - [ ] Organized project review call with relevant stakeholders after Round 1/2 of QA - [ ] Added Test Plan Approved label after reveiwing all Cypress test |
||
|---|---|---|
| .. | ||
| src | ||
| plugin.properties | ||
| pom.xml | ||