We don't have as much unit tests in place as I would like (while there are extensive unit tests for some flows, a lot of components just have one unit test which just checks that the component can be created). These manual testing flows tests the critical flows as well. These should be migrated to automated integration testing where possible, and just the flows that can't be automated should be tested manually.

1. Create new window
2. Send request with pre- and post-request scripts.
3. Manage collection (create, open query, create nested, delete).

I've encountered some weird specific behavior that occur often, so documenting here when I see such what to do

https://stackoverflow.com/a/55380827/3929126 EmptyError is thrown by the first pipe if the source observable is closed before it could emit any notification.

Fix: Use take(1) instead of first().

In the ngrx effects, use mergeMap instead of switchMap

The caller does not have permission; Please refer to https://firebase.google.com/docs/auth/admin/create-custom-tokens for more details on how to use and troubleshoot this feature.

For this error, you need to open your Google Cloud Console and add Service Account Token Creator role to your:

• App Engine default service account (this is the one that worked for me)
• Firebase service account
• Google Cloud Functions Service Agent

https://dev.to/wceolin/permission-error-when-generating-a-custom-token-on-cloud-functions-1e6c https://firebase.google.com/docs/auth/admin/create-custom-tokens#service_account_does_not_have_required_permissions

Delete all node_modules (rm -rf node_modules && rm -rf packages/*/node_modules) Remove node_modules/.cache/nx Remove angular cache (packages/altair-app/.angular)

Check that the typescript versions in all the relevant packages are the same (use yarn why typescript)

Check that you have strictNullChecks option enabled in tsconfig.json

https://firebase.google.com/docs/firestore/security/rules-query#rules_are_not_filters https://stackoverflow.com/a/71948534/3929126 Firestore compares the condition added to the query with the security rules, and they have to match. Otherwise it fails, even if the actual data set that would be returned would have met the conditions.

Always check for presence of property on resource.data before use e.g. 'ownerUid' in resource.data ? resource.data.ownerUid : false.

firebase/firebase-tools#1289

.coverage-expr:hover {
  border-bottom: 3px dashed rgb(0, 0, 0);
  cursor: default;
}

.coverage-expr[title='Expression never evaluated'] {
  background: lightyellow;
}

.coverage-expr[title^='Value true returned'] {
  background: lightgreen;
}

.coverage-expr[title^='Value false returned'] {
  background: lightcoral;
}

.coverage-expr[title^='Expression short-circuited'] {
  background: lightgrey;
}

.coverage-expr[title^='Error'] {
  background: red;
}

docker build --platform=linux/amd64 -t test-demo . docker run -p 3000:3000 test-demo

If using Cloudflare DNS, you need to setup full SSL mode instead of flexible mode

• Always create plan config in the database first
• Product should have role metadata that corresponds to PlanConfig id in the database
• Product should have type metadata set to plan
• Product should have recurring pricing

• Create a product with type metadata set to credit

https://www.codiga.io/blog/notarize-sign-electron-app/

• Temporarily replace all local packages with their file: protocol versions (so that yarn doesn't fail while searching registry for them)
• Run the update command e.g. yarn ng update @angular/core@16 @angular/cli@16 --allow-dirty --force
• Run migrate only commands if not completely successful
  • yarn ng update @angular/core --allow-dirty --force --migrate-only --from=15 --to=16
  • yarn ng update @angular/cli --allow-dirty --force --migrate-only --from=15 --to=16

Login to stripe CLI using stripe login and it should work again

• Backup the data before running the command.
• Remove all database and table creation commands from the backup file.
• Run the migration command.
• Restore it after the command.
  • Run the restore command multiple times if it fails due to foreign key constraints, until all foreign key constraints are replaced with duplicate key value errors.

env $(cat .env | xargs) pg_dump --dbname=altairgraphql-db --port=5432 --host=localhost --username=my_db_user > data.sql

yarn prisma migrate dev

psql --file=data.sql --dbname=altairgraphql-db --port=5432 --host=localhost --username=my_db_user

• add &pgbouncer=true to your connection url in order to enable pgbouncer mode in Prisma