Added basque translation

[icillero]

Summary by CodeRabbit

• New Features
  • Added Basque language support for all cookie consent and configuration UI elements, including modal texts, button labels, cookie category descriptions, and cookie information tables.

[coderabbitai]

Walkthrough

A new Basque translation file was introduced, providing localized UI text for cookie consent and configuration components. The file includes modal titles, descriptions, button labels, cookie category explanations, and table headers, ensuring comprehensive Basque language support for cookie management interfaces.

Changes

File(s)	Change Summary
src/resources/translations/eu.json	Added Basque translation JSON covering cookie consent/configuration UI, including all key strings

Poem

In Basque we now say "cookie, please,"
With buttons and labels translated with ease.
Consent and settings in a brand new hue,
For every rabbit and user, in "eu."
Hopping through modals, we localize with cheer,
Basque cookie banners—now crystal clear!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/resources/translations/eu.json (1)

43-50: Clarify 'Find out more' link label
The key cookie_table_col_link_find_out_more is set to "Esteka" (Link), but it represents 'Find out more'. Consider using "Informazio gehiago" to match the purpose and align with the find_out_more entry.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e85dfee and d62b2a1.

📒 Files selected for processing (1)

• src/resources/translations/eu.json (1 hunks)

🔇 Additional comments (1)

src/resources/translations/eu.json (1)

1-59:

Details

✅ Verification successful

Ensure key parity with other locales
Missing or extra keys in a translation file can lead to untranslated UI elements or runtime errors. Verify that this file’s key set matches the canonical locale (e.g., en.json).

Run this script to compare the key sets:

---

🏁 Script executed:

#!/bin/bash
# Compare JSON keys between English and Basque translation files
jq -r 'keys[]' src/resources/translations/en.json | sort > /tmp/en_keys.txt
jq -r 'keys[]' src/resources/translations/eu.json | sort > /tmp/eu_keys.txt
echo "Keys missing in eu.json:"
comm -23 /tmp/en_keys.txt /tmp/eu_keys.txt
echo "Extra keys in eu.json:"
comm -13 /tmp/en_keys.txt /tmp/eu_keys.txt

Length of output: 511

---

🏁 Script executed:

#!/bin/bash
# Compare JSON keys between English and Basque translation files without comm
jq -r 'keys[]' src/resources/translations/en.json | sort > /tmp/en_keys.txt
jq -r 'keys[]' src/resources/translations/eu.json | sort > /tmp/eu_keys.txt

echo "Keys missing in eu.json:"
grep -Fxv -f /tmp/eu_keys.txt /tmp/en_keys.txt || echo "(none)"

echo "Extra keys in eu.json:"
grep -Fxv -f /tmp/en_keys.txt /tmp/eu_keys.txt || echo "(none)"

Length of output: 375

---

Verified key parity: Basque locale matches English
All keys in src/resources/translations/en.json are present in src/resources/translations/eu.json and vice versa. No missing or extra keys found.