* Stylesheets
* Theme Configuration
* Options Area
* swal2 style
* Icon styling
* Fix theme not saving
* Update English
* Update messages.json
* dropdown and login logo
* btn-link and totp fix
* Organisation Styling
* Update webauthn-fallback.ts
* Fix contrast issues
* Add Paypal Container and Loading svg file
* Password Generator contrast fix
* Dark Mode Fix buttons and foreground
* Fix button hover
* Fix Styles after rebase
* Add hover on nav dropdown-item
* Disable Theme Preview
* Options Fix for Default Theme Changes
* Updated Colour Scheme
* Toast fix
* Button and Text Styling
* Options Update and Messages Fix
* Added Search Icon and Fixed Callout styling
* Add theme styling to Stripe
* Refactor logic for setting color
* Reorder logic to avoid race condition
* PayPal Loading and Misc Fix
* text-state bug fix
* Badge Colour Fix
* Remove PayPal Tagline
The colour cannot be styled so it's not visible on a dark theme
* Adding the Styling from #1131
* Update to New Design
* Form and Nav restyle
* Modal Opacity and Callout
* Nav Colours
* Missing Borders
* Light theme fix
* Improved border for listgroup
* Change Org Nav Colour
* Save theme to localStorage for persistence
* Undo change to Wired image
* !Important removal and tweaks
* Fix regression with navbar
* Light theme by default
* Refactor to use getEffectiveTheme
* Refactor theme constants to use enum
* Set theme in index.html before app loads
* Use scss selector to set logo image
* Export Sass to TS
* Update jslib
Co-authored-by: Thomas Rittson <trittson@bitwarden.com>
* starting the new pipeline model update
* updating the deploy portion of the pipeline
* adding a stub for the release notes
* removing the redundant deploy workflow
* fixing the cloud job. Adding a npm pre-cache
* updating the hashFile for the caches
* removing the cache-hit check since the logic doesn't work for node_modules
* checking out the repo in the precache
* removing the pre-cache step. Seems to slow down the pipeline overall
* ghpage-deploy with the correct input for the versions
* testing a custom action for the DCT setup
* fixing a typo
* fixing the shell issue in the custom action
* removing a conditional to run a test
* testing redaction
* fixing the weird colon inline with run issue
* commenting out the DCT for testing
* test passed. Updating the release pipeline with the new Setup DCT action
* updating the DCT setup action hash
* updating the release workflow with the linter suggestions
* Moving the web constants to the app config for more flexibility
* removing personal integrations from QA
* changing the PayPal Configuration setup to match the pattern in the services module
* removing the webConstants file after successful test
* renaming the braintree config key to something more understandable
* adding a file to the QA container to enable easy tracking the version of the currently deployed web client
* adding another visual representation of the QA version
I have a device that is blocking navigation (per chrome dev tools) on the success callback for reasons unknown. After comparing with the captcha connector (which works flawlessly), the only difference I can find is that captcha doesn't do anything else after `document.location.replace` for mobile. I'm not sure if this is the culprit but it can't hurt to try.
* Set environment URLs in webpack config.
* Provide non NULL dev server
* QA env uses the pq TLD
* Include icons in qa env
* Move base configs to develop.
local configurations should be done in the `./config/local.json` file.
* Fix config override loading to default to development
* Standardize url formatting
* Limit QA settings to those set in production
* Set self hosted in a config
* Specify cloud instead of production
Self hosted and cloud are both production environments.
The ENV setting is used to specify the env type while
NODE_ENV specifies whether development error handling and services.
* Update config instructions
* Remove invalid json
* Change env `production` references to `cloud`
* Fix formatting
