We used NEXT_PUBLIC_* env vars for values that:
- were the same across environments, and
- we wanted to easily change.
In other words, they were essentially constants. By turning them
into regular, statically-analysable, JS variables, they:
- can easily be renamed,
- are known to be defined and thus don't need non-null or type
assertions, and
- can have non-string values, removing the need to e.g. parse
integers,
- are more explicitly the same in every environment, avoiding the
temptation to attempt (and fail) to set environment-specific
env vars to override them.
* MNTOR-2650 - FAQ Section
* add premium qn and answers
* add title and see faq link
* only open one at a time
* only open one at a time
* unit tests
* add telemetry
* add test
* use link instead of btn
* add usebutton and focusring props
* remove commented out code
* let bedrock localize link
* open one at a time
* use aria hidden, aria controls for test
* use link id isntead of button id
* fix no test assertion error
* remove tabindex and align faq qn
* wrap faqqn in a button element
* use getbyrole and use regex
* use record telemetry instead
* faq specific css file
* Update src/app/(proper_react)/redesign/(public)/Faq.tsx
Co-authored-by: Vincent <Vinnl@users.noreply.github.com>
---------
Co-authored-by: Vincent <Vinnl@users.noreply.github.com>
It's fine to use NEXT_PUBLIC_* environment variables that are
defined in `.env-dist` and are the same in every environment.
However, since they are inserted at build time, they cannot be
dynamically inserted at runtime, and trying to do so will instead
inject the value they have at build time.
Here, "new users" are defined as those who are in the US, have not
yet run a data broker scan, and did not create their Monitor
account before the release of data broker scanning, as determined
by the date set in the `BROKER_SCAN_RELEASE_DATE` environment
variable.
* MNTOR-2022 - add basic Cirrus integration
* if user is not logged in, use a cookie to store random ID
* use glean from authenticated sessions, and pass user_id correctly
MNTOR-2120 - split HIBP into receiving API and processor using GCP PubSub
* add instructions for using pubsub emulator
* export knex objects so connection pools can be torn down
* move projectId, topicName, and subscriptionName to env vars
Our README suggests copying `.env-dist` to `.env`, and it contains
other values used for local development. Since this variable is
necessary to be able to sign in, it made sense to add it here.
Florian Zia
Robert Helmer
Vincent
Vincent
Kaitlyn Andres
Raphael Okafor Jr
mansaj