Website: Cleaning up content for surveys

[ssandino]

Summary by CodeRabbit

• Localization Updates
  • Refined website survey language for improved clarity
  • Added descriptive text for living location, debt, and spending categories
  • Simplified location and category names
  • Removed unnecessary qualifiers from survey text

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
public	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 31, 2024 5:29pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes focus on refining the localization JSON for a website survey. The modifications involve simplifying existing keys, removing redundant qualifiers, and adding new descriptive keys to provide clearer context for survey questions. The updates aim to enhance the clarity and readability of the survey's language by separating titles from detailed descriptions and streamlining spending category labels.

Changes

File	Changes
shared/locales/en/website-survey.json	- Added livingLocationDescV1 key - Simplified westernAreaUrbanFreetown to westernAreaUrban - Removed "(SLE 500 or above)" from debt-related titles - Added debtPersonalDescV1 and debtHouseholdDescV1 keys - Added spendingDescV1 key - Simplified spendingChoices categories

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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: 0

🧹 Nitpick comments (1)

shared/locales/en/website-survey.json (1)

97-105: Consider formatting the spending description for better readability.

While moving detailed descriptions into a single field is good, the text could be more readable.

Consider this format:

-  "spendingDescV1": "Education includes school fees, stationary, textbooks etc. Food includes for you or your household. Housing includes rent, house maintenance etc. Health care includes doctor, hospital visit, medicine etc. Transportation includes bus, taxi, poda poda, keke etc. Saving for the future includes saving it in a bank account or on a mobile money account etc. Investment includes fertilizers, tools, diesel for machinery etc.",
+  "spendingDescV1": "Categories include:\n- Education: school fees, stationary, textbooks\n- Food: for you or your household\n- Housing: rent, house maintenance\n- Health care: doctor, hospital visit, medicine\n- Transportation: bus, taxi, poda poda, keke\n- Saving for the future: bank account, mobile money account\n- Investment: fertilizers, tools, diesel for machinery",

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 427756f and bfeda1a.

📒 Files selected for processing (1)

• shared/locales/en/website-survey.json (2 hunks)

🔇 Additional comments (2)

shared/locales/en/website-survey.json (2)

45-45: LGTM! Good separation of location name and description.

The change appropriately moves the Freetown reference into the description, making the location choices clearer and more consistent.

Also applies to: 47-47

---

87-91: Verify currency code consistency.

Good separation of the monetary threshold into description fields. However, let's ensure the currency code "SLE" is used consistently throughout the codebase.

✅ Verification successful

Currency code "SLE" is used consistently throughout the codebase

The search results confirm that the currency code "SLE" is used consistently in all monetary references across the localization files. The code appears in:

• Common translations (common.json) defining "SLE" as "Sierra Leonean Leone"
• Survey questions with monetary thresholds (e.g., "SLE 500" in website-survey.json)
• Translations in multiple languages (en, fr, it, kri) maintaining the same format

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any inconsistent currency code usage
rg -i "sle|leone" --type json

Length of output: 48511

[github-actions]

Visit the preview URL for this PR (updated for commit bfeda1a):

https://si-admin-staging--pr994-sandino-survey-clean-p3fgdxfj.web.app

_{(expires Tue, 07 Jan 2025 17:18:12 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: b7b0969384059dce6ea8fad1ee1d1737e54e6676}