TODO: explore means to auto-sync localization with main Deploy on Heroku Doing so creates new commit hashes and the branches will appear out of sync. Important: Do not use "Squash" or "Rebase" to merge localization into main or vice versa. You might discuss with stakeholders which locales are priority. Note it's unlikely to have 100% of locales translated. When enough translations have been commited, you should merge localization into main, or back into your feature branch if it's not yet merged to main. You can also check translation status via the Pontoon site. Your PR should be automatically tagged with a reviewer from the Mozilla L10n team to approve your request.Īfter your updates are merged into localization, you will start to see commits from Pontoon, Mozilla's localization platform. It's best to initiate a PR when your strings are more-or-less final. Please be mindful that Mozilla localizers are volunteers, and translations come from different locales at different times – usually after a week or more. To trigger translations, open a pull request against localization. Be sure to reference the localization documentation for best practices. To add localized text, add or update the relevant. This repository has a dedicated branch for localization called. Everything should be using your localhost instance of Monitor.In the same profile, go to about:config and replace all.Set a Firefox profile to use the staging Firefox Accounts.TODO: the following functionality is disabled but the instructions are left here for posterity.įirefox's internal about:protections page ("Protections Dashboard") fetches andĭisplays breach stats for Firefox users who are signed into their FXA. coveralls.yml which contains a token – get this from another member of the Monitor team.Įnd-to-End tests use Playwright and can be run via npm run e2e. To upload coverage locally, you need a root. The unit test suite can be run via npm test.Īt the beginning of a test suite run, the test-blurts database will be populated with test tables and seed data found in src/db/seeds/Īt the end of a test suite run in CircleCI, coverage info will be sent to Coveralls to assess coverage changes and provide a neat badge. The OAUTH_CLIENT_SECRET value from a team member or someone in #fxmonitor-engineering. Should work fine running the app on You'll need to get The repo comes with a development FxA oauth app pre-configured in. Subscribe with a Firefox Account is controlled via the FXA_ENABLED To preview or test-send these emails see documentation here. Monitor generates multiple emails that get sent to subscribers. In order to enable this in GitLens, add the following to VS Code settings.json: This allows Git Blame to ignore the format commit author and show the original code author. We track commits that are largely style/formatting via. To fix all auto-fixable problems, run npx stylelint public/css/ -fix GIT Stylelint rules are based on stylelint-config-standard. To fix all auto-fixable problems, run npx eslint. A push to origin will also trigger linting.ĮSLint rules are based on eslint-config-standard. Both are installed as dev-dependencies and can be run with npm run lint. Linting and formatting is enforced via ESLint and Stylelint for JS and CSS.
0 Comments
Leave a Reply. |