-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make spanner config mandatory #956
Make spanner config mandatory #956
Conversation
Sync master
* Added the disable button option to connect to database * updated the error handling * updated the method name * resolve the comment * added UT --------- Co-authored-by: Vivek Yadav <[email protected]>
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
) {} | ||
|
||
ngOnInit(): void { | ||
this.data.isOffline.subscribe({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is non synchronous call, which I feel can call issues as we need to open the box synchronously
declarations: [HomeComponent], | ||
imports: [MatMenuModule, MatDialogModule, RouterModule.forRoot(appRoutes), HttpClientModule], | ||
imports: [MatMenuModule, MatDialogModule, RouterModule.forRoot(appRoutes), HttpClientModule,MatSnackBarModule], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: format
Hi @asthamohta As discussed, closing this PR as these changes are already incorporated in seperate PR. Thanks! |
Fixes #<issue_number_goes_here>
Currently, setting up of the Project ID and Spanner Instance ID is optional on the initial pages. With the new Verification API workflow, this is required to be mandatory. If the Spanner config are not set or invalid, the user shall receieve similar pop-up shown below before they can move forward with the schema migration.