* [web] Project collaboration events for Group Audit Logs
* Using `role` instead of `privileges` for `(send|revoke)-invite` audit log
GitOrigin-RevId: 88961afcc0580243ba9c8ab661b8fc1ca127775e
* [web] Remove new editor elements for CE/SP
Makes rendering of elements conditional or completely removes them from CE/SP:
- Subscription link is removed from settings modal
- Documentation link is present on `proxyLearn === true`
- Contact us link is present when `support` module is available (not the case for CE/SP)
* Using hidden instead of conditional rendering in settings
GitOrigin-RevId: 562563d0bc4d0ca919e336f0c13cf6b476c6cf31
* removing one class
* removing the ide redesign class
* moving error logs files from ide-redesign to orignal directory
* moving the final file of error logs
* removing the left settings menu files
* deleting left-menu-mask.tsx and related css styling
* deleting editor-left-menu-body.tsx
* deleting download-menu.tsx and related css and test and story files
* deleting actions-menu.tsx and test and story files
* deleting help-menu.tsx and test and story files
* deleting sync-menu.tsx and test and story files
* deleting settings-menu.tsx file
* deleting download-pdf.tsx
* deleting download-source.tsx
* deleting actions-copy-project.tsx
* deleting actions-word-count.tsx ans tests
* deleting help-contact-us.tsx
* deleting help-documentation.tsx and related files
* deleting help-show-hotkeys.tsx and related files
* deleting settings-auto-close-brackets.tsx
* deleting settings-auto-complete
* settings-compiler
* settings-dictionary
* deleting setting-menu files and test files
* styles:fix
* make cleanup_unused_locales
* removing some extra css and adding some comments
* npm run extract-translations
* adding settings-menu-select.tsx back
* adding back settings-overall-theme.tsx
* format:fix
* removing the settings-overall-theme.tsx and related test file
* deleting settings-menu-select and adding option type in use-editor-theme-option-group
* removing css
* deleting files and styling related to LeftMenuButton
* removing the related left editor menu files
* removing the paths
* Revert "removing the related left editor menu files"
This reverts commit 78ffbfff88cfd3ceb19946ac45a1ed6a790388f4.
* adding back the overall-theme-settings.tsx and removing the tests related to removed file
* adding back the tests with new component
* make cleanup_unused_locales
* extract-translations
* deleting the actions-manage-template.tsx file
GitOrigin-RevId: 75bcbef81740cea0452eca62f2ce52b7f10acd08
* [clsi] tweak logging for clsi-cache
- Use `clsi-cache` identifier on log line
- Add shard to context
- Record nFiles on "too many entries for tar" error
* [clsi] do not trip clsi-cache circuit breaker on ENOENT errors
These can happen when an output/compile-dir is purged while we download
files.
GitOrigin-RevId: ffa73ef312bce5232ef72e3b81966bb6e14d2255
* [monorepo] use ALLOWED_IMAGE_NAMES from production
* [web] add ALLOWED_IMAGE_NAMES to CI env
* [web] throw if ALLOWED_IMAGE_NAMES is not defined in SaaS
* [e2e] update references to ALLOWED_IMAGE_NAMES
* [web] check for ALLOWED_IMAGE_NAMES from the settings-check module
GitOrigin-RevId: 43a7343e80521e3f7e496fb771593b4c22df7d1e
* Separate heading and body font override mixins
* Separately target headings and other fonts overrides
* Separately target headings and other fonts overrides
* fix: allow independent heading font overrides without breaking existing entries
GitOrigin-RevId: b9b08316c1793fb305a8412986b78bfe5de43738
* Update test script to allow coverage to be recorded
* Collect coverage in CI
* [web] integrate coverage report with Jenkins
* [web] add coverage report for acceptance tests
* Use --all flag in vitest coverage
* Use --all flag in acceptance tests
* Switch vitest to use istanbul
* Bump versions of vitest plugins and update package-lock.json
* [web] use a dedicated parameter for coverage in unit/acceptance tests
* [web] temporarily generate HTML report and archive artifacts
* [web] do not run acceptance tests as root in CI
* [web] increase hook timeout in vitest when collecting coverage
* [web] exclude packageMapping from coverage report
* [web] use relative paths in clover reports
* [web] reduce concurrency for unit tests in CI
* [web] keep source code forever on builds
* Revert "[web] temporarily generate HTML report and archive artifacts"
This reverts commit 4c9db571
* [web] archive all the raw coverage report files
* [monorepo] update build scripts for web
* [monorepo] update package-lock.json after merge
* [web] remove spurious change
* [web] merge Jenkins parameter sections
* [web] increase hookTimeout when collecting coverage report
---------
Co-authored-by: Jakob Ackermann <jakob.ackermann@overleaf.com>
GitOrigin-RevId: 9f1ec6d38a7b037267737bec3b0bc53a0ac844af
* Extract currency conversion and rate limiting functions to helpers
* Add script to create prices from CSV for Stripe integration
* Add tests for create prices from CSV script
* Add usage documentation for create_prices_from_csv script
* Add `planCode` metadata
* Temp: Plans CSV example
* Revert "Temp: Plans CSV example"
This reverts commit 810b1ed67052f7a1a0deb20b70f14507a282fcf1.
* Various improvements to price and product creation script
---------
Co-authored-by: Tim Down <158919+timdown@users.noreply.github.com>
GitOrigin-RevId: c015c6dd904db3143781581db4210cef282a4070
* [monorepo] enable caching for eslint/prettier/stylelint
* [monorepo] speed up prettier by swapping --list-different for --check
--list-different will print each file that it processes. We have a lot
of files in the monorepo. Using --check only prints mismatching files.
Co-authored-by: Rebeka <rebeka.dekany@overleaf.com>
* [monorepo] explicitly configure prettier cache-location
This is the default location. Prettier will only discover that location
if the top level node_modules folder is writable, which is not the case
in CI. We create the .cache folder outside of docker, writable to node
inside docker.
The proper fix would be in prettier, to only check for write access in
the cache folder. Something to raise/upstream another day.
* [monorepo] run top-level format/format_fix in a single container
With the cache in place, it is much faster to use a single container.
As there is a single shared cache file, concurrent processes may see a
partially (re-)written cache file and bail out.
- all in a single container: 24s
- previous with -j4: 41s
- previous with -j8: failed due to corrupted cache file
---------
Co-authored-by: Rebeka <rebeka.dekany@overleaf.com>
GitOrigin-RevId: 7850a3a980ae6c836393d97fe56a6316ffc3fa18
