Because:
- There is logic to gracefully exit when an operations list is empty.
This Commit:
- Creates an empty file when operations lists are created.
Closes: FXA-6701
Because:
* `this` @ line 76 in `diffL1` in `diff` may be undefined rather than the class instance object since `diffL1` is a `function`.
This commit:
* Replaces `function diffL{1,2} ()` with `const diffL{1, 2} = () =>`.
Because:
* We're converting the remaining content-server Backbone views to React.
The first step in doing so is to recreate each view in React and house
it in storybook.
This commit:
* Recreates the signup_confirmed/signup_verified views in React, adds
basic tests, and adds the view to views accepted by the Ready
component.
Closes #https://mozilla-hub.atlassian.net/browse/FXA-6433
Because:
* We're converting content-server routes into React routes by extending fxa-settings
This commit:
* Creates the React version of the '/clear' page, including tests, stories, and functionality
* Adds this route to the simpleRoutes list to be served by the React app
closes FXA-6113
Because:
- The settings server functional tests have all been moved to playwright.
- The settings server integration tests run in the integration tests suites now.
This Commit:
- Phases out the settings server functional tests.
Because:
- Code would error out if the operations list was empty.
- Code should gracefully exit if asked to run an empty list of operations.
This Commit:
- Gracefully exists when operations list is empty
Because:
* An FTL contains a brand reference but does not use a brand placeable.
This commit:
* Replaces the hard coded reference with the brand placeable.
Closes#14753
Because:
- Our API expects integer values for all timing related metrics, but chrome can produce floats.
This Commit:
- Ensures that all timing metrics coming from speed strap are integers.
Because:
- Our API expects integer values for all timing related metrics, but chrome can produce floats.
This Commit:
- Ensures that all timing metrics coming from speed strap are integers.
Because:
- We've been seeing some odd behavior were 'stale' images are getting used in some cases.
This Commit:
- Disables docker layer caching for now. This seems like the safest thing to do until we fully understand what's happening in FXA-6624
Because:
* With the content-server refactor to react, a lot of new pages are being created and we want to organize them by task (ResetPassword, Signup, Signin, Pair).
This commit:
* Move all pages from the reset_password flow to a pages/ResetPassword folder.
* Update all imports within these pages.
* Group ResetPassword storybooks into a Pages/ResetPassword folder.
Closes #FXA-6604
* We're converting the remaining content-server backbone views to React. The first step (accomplished here) is to rebuild each component in React, and make that new component viewable in Storybook, with tests and localization complete.
* Adds in the `CompleteSignin` page in Storybook, with tests and l10n.
* Reworks the ResetPasswordLinkDamaged and ResetPasswordLinkExpired components to be slightly more generalized as `LinkDamaged` and `LinkExpired` components, so that they can be reused for this page. Also adds a `LinkUsed` component
* The original Backbone view would show an informative view if the link was damaged, expired, or used (or if the link was valid, but errors arose while trying to validate the signin). If a link was valid and no errors occurred, it would verify the signin and then forward the user to the appropriate page. I have added a Loading view for that case -- partially to keep the logic within that page since I think it makes sense, and partially so that the user doesn't end up in an in-between state. There's also a view to display any errors that crop up.
Closes #https://mozilla-hub.atlassian.net/browse/FXA-6353
Because:
* Need to refund subscriptions of accounts that are unverified.
This commit:
* Creates a one time script to identify accounts that created a
subscription in a specified date range.
* The script outputs separate csv files for unverified accounts,
verified accounts, and accounts with unexpected errors.
* The script has the option to refund unverified accounts.
* The script can be run with a file specifying uids or emails to skip
unverified accounts.
Closes: FXA-6551
Because:
- Our API expects integer values for all timing related metrics, but chrome can produce floats.
This Commit:
- Ensures that all timing metrics coming from speed strap are integers.
Reino Muhl
millsoper
Vijay Budhram
Vijay Budhram
Dan Schomburg
dschom
Lauren Zugai
dependabot[bot]
Bianca Danforth
Bryan Olsson
Valerie Pomerleau
Ivo Plamenac