Because:
- The CI job `Create FxA Image` ran out of memory
This Commit:
- Applies the the `--max-old-space-size=7168` node option, which should prevent the OOM.
Because:
- Fixes projects param on integration tests in flows other than test_pull_request
- Defaults to large resource class for integration tests (for now)
Because:
* We'd like to be able to use Nest-Typed-Config with a structured config file that can be validated at runtime if desired.
This commit:
* Adds a typed config class for the Contentful client.
* Reference PR: https://github.com/mozilla/fxa/pull/15724
Closes #No ticket
Because:
- Not all CI operations where taking advantage of NX caches
This Commit:
- Adjusts nx.json config to ensure correct caching behavior
- Adjusts nx.json config to ensure proper target chains. ie build is dependent on pre-build
- Uses nx to directly run integration tests
- Uses nx to directly run unit tests
- Phases out dependency on generated .list files
- Ensures 'start up' for services for functional tests is done with nx and uses nx caches.
- Creates nx tags to facilitate test commands
- Fixes linter errors encountered
- Updates docker images to nx for builds
- Updates nx ignore files
Because:
* The paypal client config is a basic interface, and we'd like to be
able to use Nest-Typed-Config with a structured config file.
This commit:
* Adds a typed config class for the paypal client.
Because:
* We want to use the latest typescript features.
This commit:
* Updates to TypeScript 5.2.2.
* Updates to Node 18.17.1 as OOM would occur frequently with 18.14.
* Updates CI to use a large instance with increased memory for Node.
Because:
* We want to easily be able to consume library classes within NestJS.
Adding the injectable decorator to all library classes means we can do
so with ease, but also doesn't prevent us from using the class outside
of the NestJS DI system.
* We want all dependencies (such as nest) centralized to the main
package.json
This commit:
* Adds the injectable decorator to every library class.
* Centralizes the NestJS dependency to the root package.json.
Closes: no relevant issue - polish PR.
Because:
- We need to know if an accounts password was set
This Commit:
- Adds a row for Password Set
- Exposes the verifierSetAt field to the front end
- Uses verifierSetAt to determine if a password was set
- Fixes bug where dev mode wasn't starting due wrong path
- Fixes bug where StrictMode was stopping lazy queries from executing
Because:
* We were only rendering the default service name
This commit:
* Sets the service name from the integration
* Sets up mock integration functions for that page and creates interfaces file for that page
closes FXA-8141
Because:
- Service name was blank for connected device after going through password reset flow
This Commit:
- Makes sure user agent propagates from graphql to auth-server
- Adds tests for our gql decorator class
- Adds logic to functional test to ensure the service name isn't blank
Because:
* Some validation checks are incorrect since params are always strings unless transformed, causing a blank page to show in some cases
This commit:
* Uses the 'isBooleanString' decorator instead of 'isBoolean' until we can better validate with (probably) a custom decorator
Because:
* We want to have a single place to manage account related operations in
the database layer.
This commit:
* Adds a new AccountManager class and account package.
Closes #FXA-6623
Because:
* auth-server was failing to start after deploy due to tsconfig paths
not resolving to the relevant libraries.
This commit:
* Adds a tsc-alias to build step to resolve alias paths to relative
paths.
Closes
Because:
- hashing the uid is async (`crypto.subtle.digest`), thus making the
Glean ping calls async. And preferably we don't block the UI on
metrics. However, we cannot overlap (not await) multiple Glean
pings. When that happened with the successful registration
submission event overlapping the registration confirmation view
event, we "lost" all the succession registration event because that
event has an empty event name. And the confirmation view event was
submitted with the properties of the successful registration
submission event.
This commit:
- calls and awaits the ping submissions in order inside GleanMetrics