fxa/.gitignore

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

170 строки
3.3 KiB
Plaintext
Исходник Обычный вид История

# Repo root
/loop-server
/syncserver
/selenium-*
/servers_android.json
/pm2
/dump.rdb
external
2014-11-05 04:21:04 +03:00
# Secrets
.env
.env.local
.env.development.local
.env.test.local
.env.production.local
2023-09-26 02:29:45 +03:00
*.env
.keys
public-key.json
secret-key.json
secret*
*.gpg
secrets.json
# Build and temp files
**/build
**/dist
**/temp
**/version.json
**/storybook-static
*.sass-cache
**/schema.gql
*.map
2020-07-10 01:26:36 +03:00
*.swp
.es5
.es5cache
/artifacts
2020-04-09 17:57:05 +03:00
.last-audit
.eslintcache
storybooks-publish
tsconfig.tsbuildinfo
tailwind.out.*
.idea
# Dependencies
**/node_modules
**/browser_modules
/.pnp
.pnp.js
2019-04-10 09:11:01 +03:00
# Logging
*.log*
**/logs
# Testing
coverage.html
**/coverage
**/.nyc_output
test-results.xml
# Local configuration
/_dev/firebase/.config
# System files
*~
\#*\#
.\#*
.DS_Store
Thumbs.db
# Yarn
.yarn/cache
.yarn/berry
.yarn/build-state.yml
.yarn/install-state.gz
# nektos/act - Github Actions
/bin/
# Glean CLI will install glean_parser into a .venv in the dir from which the
# command is called
.venv
## Package-specific ##
# circleci
.circleci/local.yml
# browserid-verifier
packages/browserid-verifier/loadtest/venv
packages/browserid-verifier/loadtest/*.pyc
feature(admin-panel): Add nestjs subscription service Because: - We want to display account subscription data in the admin panel. This Commit: - Hooks up the Account React component to real subscription data.
 - Fixes a long standing issue with Knex in the admin panel! Knex instance is now bound to BaseAuthModel and repurposed across derived classes. - Introduces a subscription module that provides the nestjs services necessary to retrieve subscription data. - Introduces a subscription service that acts as the primary point of request for subscription data. - Introduces stripe service so that stripe can be dependency injected. - Introduces firestore service so that firestore can be dependency injected. - Introduces play store service so that play store accessor can be dependency injected. - Introduces app store service so that app store accessor can be dependency injected. - Introduces subscription formatters that unify subscription dtos into standard response format. - Improves config setup to allow for local.json and secrets.json files to be used. - Introduces configuration settings so that underlying services can be accessed. - Introduces feature flags to disable queries to underlying stripe, google or apple apis. - Hoists a couple joi validators up to fxa-shared for reuse. - Breaks out an auxiliary method that can determine product ids given iapType and a plan. This exists in in stripe.ts in fxa-shared. (The previous code had zero dependence on the stripe class, which made this possible. This was primarily done for testing purposes.) - Exposes a couple more fields on AppStoreSubscriptionPurchase to support subscription formatting. - Fixes typing on MozSubscription.endedAt. Value is allowed to be null | undefined. - Adds tests and achieves 90+ percent test coverage on all new code. - Adds reusable mocks for standard services to facilitate testing. - Updates readme with info about subscriptions, configuration, feature flags, and testing. - Updates pm2.js with better defaults to support subscription service.
2022-05-24 18:54:17 +03:00
# fxa-admin-server
packages/fxa-admin-server/src/config/local.json
feature(admin-panel): Add nestjs subscription service Because: - We want to display account subscription data in the admin panel. This Commit: - Hooks up the Account React component to real subscription data.
 - Fixes a long standing issue with Knex in the admin panel! Knex instance is now bound to BaseAuthModel and repurposed across derived classes. - Introduces a subscription module that provides the nestjs services necessary to retrieve subscription data. - Introduces a subscription service that acts as the primary point of request for subscription data. - Introduces stripe service so that stripe can be dependency injected. - Introduces firestore service so that firestore can be dependency injected. - Introduces play store service so that play store accessor can be dependency injected. - Introduces app store service so that app store accessor can be dependency injected. - Introduces subscription formatters that unify subscription dtos into standard response format. - Improves config setup to allow for local.json and secrets.json files to be used. - Introduces configuration settings so that underlying services can be accessed. - Introduces feature flags to disable queries to underlying stripe, google or apple apis. - Hoists a couple joi validators up to fxa-shared for reuse. - Breaks out an auxiliary method that can determine product ids given iapType and a plan. This exists in in stripe.ts in fxa-shared. (The previous code had zero dependence on the stripe class, which made this possible. This was primarily done for testing purposes.) - Exposes a couple more fields on AppStoreSubscriptionPurchase to support subscription formatting. - Fixes typing on MozSubscription.endedAt. Value is allowed to be null | undefined. - Adds tests and achieves 90+ percent test coverage on all new code. - Adds reusable mocks for standard services to facilitate testing. - Updates readme with info about subscriptions, configuration, feature flags, and testing. - Updates pm2.js with better defaults to support subscription service.
2022-05-24 18:54:17 +03:00
# fxa-auth-server
packages/fxa-auth-server/sandbox
packages/fxa-auth-server/config/key.json
packages/fxa-auth-server/config/oldKey.json
packages/fxa-auth-server/config/vapid-keys.json
packages/fxa-auth-server/test/load/bin
packages/fxa-auth-server/test/load/lib*
packages/fxa-auth-server/test/load/include
packages/fxa-auth-server/test/scripts/bulk-mailer/nodemailer-mocks/test_output
packages/fxa-auth-server/*.pyc
packages/fxa-auth-server/server.pot
packages/fxa-auth-server/.mail_output
packages/fxa-auth-server/fxa-content-server-l10n
packages/fxa-auth-server/lib/senders/emails/css
packages/fxa-auth-server/public/locales
packages/fxa-auth-server/vendor
# fxa-content-server
packages/fxa-content-server/pids
packages/fxa-content-server/results
packages/fxa-content-server/lib-cov
packages/fxa-content-server/app/styles/main.css
packages/fxa-content-server/app/scripts/processed
packages/fxa-content-server/server/config/local.json
packages/fxa-content-server/app/i18n
packages/fxa-content-server/fxa-content-server-l10n/
packages/fxa-content-server/locale/*/*/*.po
packages/fxa-content-server/rerun.txt
packages/fxa-content-server/.tmp
packages/fxa-content-server/.tscompiled
packages/fxa-content-server/public/locales
# fxa-customs-server
packages/fxa-customs-server/test/mocks/temp.netset
# fxa-payments-server
packages/fxa-payments-server/fxa-content-server-l10n/
packages/fxa-payments-server/public/locales
packages/fxa-payments-server/test
# fxa-profile-server
packages/fxa-profile-server/var
packages/fxa-profile-server/BUCKET_NAME
# fxa-react
packages/fxa-react/**/*.js
!packages/fxa-react/**/gruntfile.js
packages/fxa-react/**/*.d.ts
!packages/fxa-react/pm2.config.js
packages/fxa-react/fxa-content-server-l10n/
packages/fxa-react/public/locales
packages/fxa-react/test/
# fxa-settings
packages/fxa-settings/fxa-content-server-l10n/
2021-02-22 23:42:49 +03:00
packages/fxa-settings/public/locales
packages/fxa-settings/legal-docs/
packages/fxa-settings/public/legal-docs
packages/fxa-settings/test/
Library
.node
process.yml
task(CI): build, unit test, and integration test jobs Because: - We wanted to run a few preliminary checks before proceeding to more expensive CI jobs. Checks include: - Compiling typescript in commonly referenced workspace packages - Linting code that has changed - Executing Unit Tests for code that has changed - We wanted to partition test operations into unit tests, and integration tests. Unit tests can be run relatively quickly and require no additional infrastructure. Integration tests require additional infrastructure and generally have longer execution times. Now that jobs are blocked from running until preliminary checks pass, one of which is unit tests, it is important to draw a distinction between these two types of tests. - We want to avoid unnecessary yarn installs and typescript compilations, which are time consuming. - We want to make sure that test results are published and failing tests can be easily viewed in the CI. This Commit: - Creates a build-and-validate job in the CI that builds, lints, and unit tests code prior to running any other jobs. - Creates unit-test job in CI config - Creates integration-test job in CI config - Removes redundant calls to compile workspace packages. These are now built up front, cached, and restored as needed for future runs. - Extends the create-lists script functionality to generate commands that can be executed with the parallel command. - Removes unnecessary yarn install operations. Invoking yarn workspace focus results in a yarn install. In the case of running tests this is largely unnecessary, because we already do a yarn install in the base-install step. - Make sure test results are exported as junit xml so the CI can report back on tests that were failing. This was done for a couple workspace packages, but many were lacking the capability. All test:unit and test:integration npm scripts now export this data. - Fixes the following issues encountered along the way: - Adds logs to monitor heap usage of jest tests. Some jest tests are still using a lot of memory. - Moves a few slow / long running tests from unit test to integration tests. - Ensures that jest.transform for ts-jest is always instructed to have the config option isolateModules is set to true. This definitely decreases memory overhead and resolves some of the OOM errors we were hitting. It was configured in some places but not everywhere. - Exports test results files for all tests - Exports all test artifacts - Uses gnu parallel to run tests in parallel. Turns out yarn workspaces foreach would give a false positive when an OOM was encountered. Fortunately, the parallel command offered an acceptable work around, and even offers some nice features like the load argument, which allows to control test execution a bit more efficiently.
2023-01-10 23:52:01 +03:00
.lists
**/config/gql/allowlist
configs/gql/allowlist
!configs/gql/allowlist/gql-playground.json
# Next.js
.next
tmp