Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make language choice peristent for users #1075
base: main
Are you sure you want to change the base?
Make language choice peristent for users #1075
Changes from all commits
6daa48d
29aaf52
26e7669
4068c0b
061a4e8
3b24a84
acdbba6
18f898b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/common.test.ts:72:4 › Tests on domains item › Tests on domains item details › Domains item details are showing properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/common.test.ts:72:4 › Tests on domains item › Tests on domains item details › Domains item details are showing properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/compliance-assessments.test.ts:8:1 › compliance assessments scoring is working properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/compliance-assessments.test.ts:8:1 › compliance assessments scoring is working properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/compliance-assessments.test.ts:8:1 › compliance assessments scoring is working properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/compliance-assessments.test.ts:8:1 › compliance assessments scoring is working properly
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/libraries.test.ts:4:1 › every library can be loaded
Check failure on line 33 in frontend/tests/utils/base-page.ts
GitHub Actions / functional-tests (3.11, chromium)
[chromium] › functional/detailed/libraries.test.ts:4:1 › every library can be loaded