Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix: Update es.json to resolve{{name}} bug#9889

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
alejndr0 wants to merge3 commits intoappwrite:main
base:main
Choose a base branch
Loading
fromalejndr0:patch-1

Conversation

alejndr0
Copy link

@alejndr0alejndr0 commentedMay 25, 2025
edited by coderabbitaibot
Loading

What does this PR do?

image

Fix Spanish bug where the user was not properly rendered, showing '{{name}}' instead of '{{user}}' as specified in thedocumentation.

Checklist

  • Have you read theContributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

Summary by CodeRabbit

  • Bug Fixes
    • Updated Spanish email templates to use a consistent placeholder for the recipient's name in verification and password recovery emails.

@coderabbitaicoderabbitai
Copy link

coderabbitaibot commentedMay 25, 2025
edited
Loading

Walkthrough

The Spanish localization file was updated to change the placeholder variable in the greeting lines of verification and password recovery email templates from "{{name}}" to "{{user}}". No other keys or text were modified.

Changes

FileChange Summary
app/config/locale/translations/es.jsonUpdated email greeting placeholders from "{{name}}" to "{{user}}".

Poem

In Spanish emails, a tweak so slight,
"{{name}}" becomes "{{user}}", just right.
Greetings now shine with a brand new hue,
For every message that hops on through.
¡Hola, usuario! The rabbits cheer,
For tidy templates, far and near.
🐇✨


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and betweena955b6c and4ef5ec5.

📒 Files selected for processing (1)
  • app/config/locale/translations/es.json (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/config/locale/translations/es.json
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: scan

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
🪧 Tips

Chat

There are 3 ways to chat withCodeRabbit:

  • 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 oursupport 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 togenerate 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.

Documentation and Community

  • Visit ourDocumentation for detailed information on how to use CodeRabbit.
  • Join ourDiscord Community to get help, request features, and share feedback.
  • Follow us onX/Twitter for updates and announcements.

@alejndr0alejndr0 changed the titleUpdate es.jsonfix: Update es.json to resolve{{name}} bugMay 25, 2025
Copy link

@coderabbitaicoderabbitaibot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
app/config/locale/translations/es.json (2)

7-7:Placeholder updated to{{user}} in verification email template
The Spanish translation now correctly uses the{{user}} variable as per Appwrite’s email template syntax.

Consider removing the extra period before the comma to improve punctuation consistency:

-"emails.verification.hello": "Hola, {{user}}.,"+"emails.verification.hello": "Hola, {{user}},"

19-19:Placeholder updated to{{user}} in recovery email template
This change aligns with the official template variable specification.

As a minor refinement, you may also remove the redundant period before the comma for correct Spanish punctuation:

-"emails.recovery.hello": "Hola, {{user}}.,"+"emails.recovery.hello": "Hola, {{user}},"
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between4c5094d anda955b6c.

📒 Files selected for processing (1)
  • app/config/locale/translations/es.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: scan

@github-actionsGitHub Actions
Copy link

github-actionsbot commentedMay 25, 2025
edited
Loading

Security Scan Results for PR

Docker Image Scan Results

PackageVersionVulnerabilitySeverity
binutils2.42-r0CVE-2025-0840HIGH
libexpat2.6.4-r0CVE-2024-8176HIGH
libxml22.12.7-r0CVE-2024-56171HIGH
libxml22.12.7-r0CVE-2025-24928HIGH
libxml22.12.7-r0CVE-2025-27113HIGH
libxml22.12.7-r0CVE-2025-32414HIGH
libxml22.12.7-r0CVE-2025-32415HIGH
pyc3.12.9-r0CVE-2024-12718HIGH
pyc3.12.9-r0CVE-2025-4138HIGH
pyc3.12.9-r0CVE-2025-4330HIGH
pyc3.12.9-r0CVE-2025-4517HIGH
python33.12.9-r0CVE-2024-12718HIGH
python33.12.9-r0CVE-2025-4138HIGH
python33.12.9-r0CVE-2025-4330HIGH
python33.12.9-r0CVE-2025-4517HIGH
python3-pyc3.12.9-r0CVE-2024-12718HIGH
python3-pyc3.12.9-r0CVE-2025-4138HIGH
python3-pyc3.12.9-r0CVE-2025-4330HIGH
python3-pyc3.12.9-r0CVE-2025-4517HIGH
python3-pycache-pyc03.12.9-r0CVE-2024-12718HIGH
python3-pycache-pyc03.12.9-r0CVE-2025-4138HIGH
python3-pycache-pyc03.12.9-r0CVE-2025-4330HIGH
python3-pycache-pyc03.12.9-r0CVE-2025-4517HIGH
sqlite-libs3.45.3-r1CVE-2025-29087HIGH
xz5.6.2-r0CVE-2025-31115HIGH
xz-libs5.6.2-r0CVE-2025-31115HIGH
golang.org/x/cryptov0.31.0CVE-2025-22869HIGH

Source Code Scan Results

🎉 No vulnerabilities found!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

1 participant
@alejndr0

[8]ページ先頭

©2009-2025 Movatter.jp