-
Notifications
You must be signed in to change notification settings - Fork 95
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
Fix setting reading the search language cookie #1693
Conversation
Translations can be maintained with the Symfony-Lokalise combination (pull, push, extract) but not yet by extracting from Vue code (#1648) At first, there was some uncertainty about whether the system was actually updating the data correctly (deletion in Lokalise -> deletion locally as well), but it seems that it worked correctly after all. Although the feature branch can be merged, further testing should still be done just to be sure. Add cypress tests for alphabetical index + add new test vocab Add cypress test for alt labels Add cypress files for alphabetical index and hierarchy Move alphabetical index cypress tests from vocab-home.cy.js + add checks for spinners Change test vocab name Fix uriSpace Fix uri space in test vocab
…ant cypress test to avoid a false positive test result
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think nothing sets the SKOSMOS_LANGUAGE cookie anymore, though. It looks like it's becoming dead code in 3.0. |
You're right that it's not being set by the current Skosmos 3 code. In the Skosmos 2 code, we set event handlers for the UI language selection links: Skosmos/resource/js/docready.js Lines 488 to 494 in 6b9b380
I think the same should be done for Skosmos 3. I can open a new issue about this. |
Opened a new issue #1696 |
Closing this PR, as the preferred solution was to get rid of the search language cookie (PR #1720). For example, the content language state of one vocabulary might not make sense when switching to another vocabulary with different supported languages. Better to handle search language with clang url parameter. |
Reasons for creating this PR
There was a bug reading the content language cookie, due to a method not being updated to follow the new cookie convention. This PR is built upon #1689 .
Link to relevant issue(s), if any
Description of the changes in this PR
Changed the name of the cookie
Known problems or uncertainties in this PR
Checklist
.sr-only
class, color contrast)