8000 Add new logo and i18n for HS by adamkecskes · Pull Request #7823 · codecombat/codecombat · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add new logo and i18n for HS #7823

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

Merged
merged 2 commits into from
Nov 13, 2024

Conversation

adamkecskes
Copy link
Collaborator
@adamkecskes adamkecskes commented Nov 11, 2024

client for https://github.com/codecombat/ai/pull/300

Summary by CodeRabbit

  • New Features

    • Introduced new localization entries for enhanced user engagement and clarity.
    • Added new phrases related to AI features, such as "Learn With AI" and "Create With AI."
    • Included updated FAQs and instructional content for both students and educators.
  • Enhancements

    • Updated terminology for AI features to promote user interaction (e.g., "Create AI" to "Create With AI").
    • Improved error messages for clearer guidance during user interactions.
  • Bug Fixes

    • Removed outdated or redundant localization entries for streamlined content.

Copy link
Contributor
coderabbitai bot commented Nov 11, 2024

Walkthrough

The pull request introduces extensive modifications to the localization strings in app/locale/en.js. Key updates include the addition of new entries, revisions of existing strings for clarity, and the removal of outdated content. The changes reflect a focus on enhancing user engagement and educational support, particularly through AI integration. Terminology has been updated to promote a more inviting tone, and new FAQs and instructional content have been added to improve resourcefulness for users.

Changes

File Change Summary
app/locale/en.js - Added new localization entries for various features.
- Modified existing strings for clarity and engagement, especially regarding AI features.
- Removed outdated or redundant entries to streamline the file.
- Updated terminology to reflect a more user-friendly approach.

Possibly related PRs

Suggested reviewers

  • mrfinch

🐰 In the meadow, changes bloom,
New words and phrases chase the gloom.
With AI's help, we guide the way,
For students and teachers, brightening the day!
So hop along, explore and see,
A world of learning, wild and free! 🌼✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

warning eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning eslint-plugin-script-tags@0.5.0: Now published as @mapbox/eslint-plugin-script-tags
warning blockly > jsdom > abab@2.0.6: Use your platform's native atob() and btoa() methods instead
warning blockly > jsdom > data-urls > abab@2.0.6: Use your platform's native atob() and btoa() methods instead
warning blockly > jsdom > domexception@4.0.0: Use your platform's native DOMException instead
warning treema > express > mkdirp@0.3.3: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning treema > express > connect@2.7.2: connect 2.x series is deprecated
warning treema > express > connect > formidable@1.0.11: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
warning vue@2.7.10: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
warning jasmine > glob@3.2.11: Glob versions prior to v9 are no longer supported
warning jasmine > glob > minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning karma > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning karma > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning karma > socket.io > debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
warning karma > tmp > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning karma > socket.io > engine.io > debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
warning karma > socket.io > socket.io-parser > debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
warning pug > pug-filters > constantinople > babel-types > babel-runtime > core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning standard > eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning @babel/plugin-proposal-optional-chaining@7.21.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
error treema@0.0.0: The engine "node" is incompatible with this module. Expected version "0.8.x". Got "22.9.0"
error Found incompatible module.


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

Copy link
Contributor
@coderabbitai coderabbitai bot 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

🧹 Outside diff range and nitpick comments (4)
app/locale/en.js (4)

Line range hint 8-24: Verify translations for new entries

Several new translation entries have been added under the ozaria_home namespace, such as subtitle, heading_subtitle, item_list_p, etc.

Please ensure these new English translations accurately convey the intended messaging for the Ozaria home page.


Line range hint 29-42: Review updated translations

The translations for entries like global_subtitle1, global_subtitle2, etc. under ozaria_home have been updated.

Please review these changes to confirm they are accurate and read naturally in English.


Line range hint 44-45: Verify new translation entry

A new translation individual_users_not_supported has been added.

Please confirm this new English message is worded appropriately to convey that Ozaria is for classrooms only.


6093-6094: New translation entries added

Two new translation entries edit and delete have been added under the hackstack namespace.

Please verify these single word translations are sufficient in the context they will be used.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between dd5bb39 and 03d4fea.

📒 Files selected for processing (1)
  • app/locale/en.js (1 hunks)
🔇 Additional comments (5)
app/locale/en.js (5)

Line range hint 1-2: Looks good!

The module exports syntax is correct.


Line range hint 4-6: Translations look appropriate

The English translations for the nativeDescription and englishDescription fields are correct.


Line range hint 26-27: Translations look good

The translations for the pd_blurb entry look good, with the __pd__ placeholder used correctly.


Line range hint 47-48: Translation looks good

The translation for the accounts_merge_confirmation entry looks good.


Line range hint 50-6092: Skipped reviewing unchanged code

The code in these line ranges does not appear to have any changes. Skipping detailed review.

Copy link
Contributor
@coderabbitai coderabbitai bot 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

🧹 Outside diff range and nitpick comments (5)
app/locale/en.js (5)

Line range hint 1-6088: Standardize string interpolation syntax

The file uses mixed string interpolation styles - both __variable__ and {variable}. For example:

- diplomat_pitch_body: "We develop CodeCombat in English, but we already have players all over the world. Many of them want to play in {English} but don't speak English..."
+ diplomat_pitch_body: "We develop CodeCombat in English, but we already have players all over the world. Many of them want to play in __english__ but don't speak English..."

Should standardize on the __variable__ syntax used by majority of strings for consistency.


Line range hint 1-6088: Standardize text formatting approach

The file mixes HTML and markdown formatting styles. For example:

- mission_description_1: "<strong>Programming is magic</strong>. It's the ability to create things from pure imagination."
+ mission_description_1: "**Programming is magic**. It's the ability to create things from pure imagination."

- learn_more_modal: 'Teacher accounts on CodeCombat have the ability to monitor student progress, assign licenses and manage classrooms. Teacher accounts cannot be a part of a classroom - if you are currently enrolled in a class using this account, you will no longer be able to access it once you update to a Teacher Account.',
+ learn_more_modal: "Teacher accounts on CodeCombat have the ability to monitor student progress, assign licenses and manage classrooms.\n\nTeacher accounts cannot be a part of a classroom - if you are currently enrolled in a class using this account, you will no longer be able to access it once you update to a Teacher Account."

Should standardize on markdown formatting for consistency and readability:

  • Use **text** for bold instead of <strong>
  • Use [text](url) for links instead of <a>
  • Use newlines instead of <br> tags

Line range hint 1-6088: Fill in missing translations

Several strings are missing translations or have placeholder values:

App_alt: '',
faq_7_answer: 'TBA',

Please provide translations for all empty strings and replace placeholder values with actual content.


Line range hint 1-6088: Fix typos and grammatical issues

Found several text quality issues:

- separated_by_comma: "Function calls paramaters must be seperated by `,`s"
+ separated_by_comma: "Function call parameters must be separated by commas"

- error_segmentation_fault: 'Segmentation Fault `__offset__`.',
+ error_segmentation_fault: 'Segmentation Fault at offset `__offset__`.'

Please review and correct typos, grammar, and improve readability where needed.


Line range hint 1-6088: Standardize terminology usage

Found inconsistent terminology throughout the file:

  • Mixed usage of "student" and "learner"
  • Inconsistent capitalization of product names (e.g. "CodeCombat", "Codecombat", "codecombat")
  • Varying terms for same concepts (e.g. "teacher"/"educator", "class"/"classroom")

Should establish and follow a terminology style guide to maintain consistency.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 03d4fea and 9897a21.

📒 Files selected for processing (1)
  • app/locale/en.js (1 hunks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0