Pull latest from fork head #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Format * Auto start the emulator * Fix `setDataconnect` not updating anything * Add button to enable postgress & `run` codelenses. If a postgres connectionString is missing, prompts for one, and save it in the RC file. --------- Co-authored-by: Harold Shen <hlshen@google.com>
* Make vector warnings best effort * Rework build error behavior, and clean up unrecognized arg logs * Update src/emulator/dataconnectEmulator.ts Co-authored-by: Yuchen Shi <yuchenshi@google.com> * Add back in auto_download --------- Co-authored-by: Yuchen Shi <yuchenshi@google.com>
* first progress * Handle fresh from console cases * Add changelog * formats * pr fixes
`fdc-db` is not a valid Postgres identifier and requires quoting, which makes SQL statements annoying.
* emulator bump * changelog * changelog
* add node22 support and add newline before runtime list * add changelog entry * regen schema --------- Co-authored-by: joehan <joehanley@google.com>
* Bump FDC emulator to v1.2.0. * Minor changelog update. --------- Co-authored-by: joehan <joehanley@google.com>
* Fix inquirer error. * Run vscode tests in the CI * Build dist before running tests * Run install before running tests * debug * test * Try? * Attempt 2 * Try2 * Try with display * Try using windows platorm * Run npm i in root folder first * Remove DiSPLAY * Fix runTest * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review --------- Co-authored-by: Harold Shen <hlshen@google.com> Co-authored-by: joehan <joehanley@google.com>
#7264) * fix: support deployment of an Angular app using legacy browser builder * feat: add entry to changelog * fix: format * fix: improve the code based on the comments
* initial impelemention of sql connection action * add ConfigureEmulator api to dataconnectEmulatorClient * Autoconnect to postgres when not in VSCE (#7266) * Autoconnect to postgres when not in VSCE * Format * Return values * address comments * format * format and add comment --------- Co-authored-by: joehan <joehanley@google.com>
* changelog * update v --------- Co-authored-by: joehan <joehanley@google.com>
* Fixing file mode on new scripts * Further fixes to release script
* Adding gsutil to our builder image * Commit vscode changelog too
* update 0.2.4 * update 0.2.4 * 0.2.5
* Wait for emualtor to start to initialize client * formats * Formatted, and added better error message on bad pgconn string * remove log
…vision (#7275) * come back later comment * change log * changelog * m * Update CHANGELOG.md * Make `firebase init dataconnect` not wait for CSQL provisioning * catch state=failed * m * Update src/gcp/cloudsql/cloudsqladmin.ts --------- Co-authored-by: joehan <joehanley@google.com>
…:diff` (#7633) * Compat mode support. * Support handling schema validation options in `diff`. * Fix build. * Format. * Don't output second set of diffs if they're equal to the first. * Address review comments. * Tweak output logs.
* Bump FDC local toolkit to v1.3.6. * Bump versions.
…7611) * Update message when users try to update from 1st to 2nd Gen function using the same function name. CLI has always block the transition 1st Gen to 2nd Gen in the CLI - change here simply update the product name and point users to our public doc that documents changes necessary to transition to 2nd gen function. Aside: Cloud Run functions doesn't allow for 1st and 2nd gen functions to share the same name. * messaging nit. * Say 'see' instead of 'please'. --------- Co-authored-by: joehan <joehanley@google.com>
* feat: change supported range for Angular framework * feat: update changelog * feat: update supported range
* Update the Firestore init() flow to handle non-default databases, by allowing the user to input the name of the database they want to initialize. This is a catch for older projects created in Cloud, which have a (default) non-Firestore Native database in their projects before they add Firebase. * Update the Firestore init() flow to handle non-default databases, by allowing the user to input the name of the database they want to initialize. This is a catch for older projects created in Cloud, which have a (default) non-Firestore Native database in their projects before they add Firebase. * Changelog --------- Co-authored-by: joehan <joehanley@google.com>
…e` and `deploy` (#7639) * Support handling schema validation options in `diff`. * Format. * Don't output second set of diffs if they're equal to the first. * Update dataconnect:sql:migrate * Fix my failed rebase lol * Finish handling schemaValidation mode in `dataconnect:sql:migrate`. * Fix setSchemaValidationMode. * Concat follow-up strict diffs, instead of replacing compat diffs. * Don't display purely optional changes with flag. * Pass `schemaValidation` into `deploy` command. * Address review comments.
* Make `firebase init` for FDC work better with Spark projects. * Don't provision CloudSQL instance if billing is not enabled. * Remove experiment flag gating. * Enable other APIs besides compute.googleapis.com.
#7589) * update data connect client, dataplaneclient, and emulator client to v1beta * update tests
* Update FDC local toolkit to v1.3.7. * Add PR number to changelog.
* Switch primaryDatasource -> datasources * ?. * primaryDatasource -> postgresDatasource
* initial grant commands * Add some checks and fix linting * Address comments and cleanup / error messages * Add fdc grant commands changelog
* Ignore invalid connector errors in Using Google Analytics in DEBUG mode. Emulators (+ UI) events will be shown in GA Debug View only. Error: No currently active project. To run this command, you need to specify a project. You have two options: - Run this command with --project <alias_or_project_id>. - Set an active project by running firebase use --add, then rerun this command. To list all the Firebase projects to which you have access, run firebase projects:list. To learn about active projects for the CLI, visit https://firebase.google.com/docs/cli#project_aliases. * Update schema migration prompt wording. * Another prompt message wording update. --------- Co-authored-by: joehan <joehanley@google.com>
* Add --dry-run to deploy * Format * Format * pr fixes * PR fixes for functions and extensions * Merging in master * fix test failure * Add diffSchema to dataconnect dry run, better end message * format
* Add firebase ext:sdk:install command
Co-authored-by: joehan <joehanley@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.