Skip to content
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

Innovation library name changes and 1 fix #7281

Closed
wants to merge 2 commits into from

Conversation

DonnaDuiker
Copy link
Contributor

@DonnaDuiker DonnaDuiker commented Dec 5, 2024

Describe the background of your pull request

Changing these names:
Innovation library --> Template library

Best Practices (in menu) --> Template library

Innovation pack --> Template pack
As described here: https://github.com/orgs/alkem-io/projects/22/views/5?pane=issue&itemId=89200104&issue=alkem-io%7Cclient-web%7C7265

1 sentence did not make sense anymore after challenge was changed to subspace, as mentioned here: https://github.com/orgs/alkem-io/projects/22/views/5?pane=issue&itemId=88839685&issue=alkem-io%7Cproduct%7C1387

Additional context

Add any other context

Governance

  • Documentation is added
  • Test cases are added or updated

By submitting this pull request I confirm that:

Summary by CodeRabbit

  • New Features

    • Updated terminology across the platform from "Innovation" to "Template," enhancing clarity for users.
    • Introduced a "Template Library" section, replacing the previous "Innovation Library."
  • Bug Fixes

    • Improved error messages and notifications to align with the new terminology.
  • Documentation

    • Enhanced descriptions and user interface elements for better user comprehension and consistency.

@DonnaDuiker DonnaDuiker requested a review from ccanos December 5, 2024 10:01
Copy link

coderabbitai bot commented Dec 5, 2024

Walkthrough

This pull request implements extensive updates to translation files across multiple languages for the Alkemio platform. The primary focus is on renaming terms related to "Innovation" to "Template," including the "Innovation Library" being changed to "Template Library" and "Innovation Packs" to "Template Packs." These changes are reflected in various user interface elements, descriptions, and error messages, aiming for consistency in terminology and clarity in user experience.

Changes

File Path Change Summary
src/core/i18n/bg/translation.bg.json Updated terminology from "Innovation library" to "Template Library" and "Innovation Packs" to "Template Packs." Enhanced clarity in descriptions and UI elements.
src/core/i18n/de/translation.de.json Changed "Innovation library" to "Template library" and updated descriptions and button labels accordingly.
src/core/i18n/en/translation.en.json Renamed "Innovation Packs" to "Template Packs" throughout the file, including in various sections like common and plansTable.
src/core/i18n/es/translation.es.json Modified "Innovation Library" to "Template Library" and adjusted related descriptions and UI elements for consistency.
src/core/i18n/fr/translation.fr.json Changed "Innovation library" to "Template library" with corresponding updates to descriptions and UI elements.
src/core/i18n/ua/translation.ua.json Updated terminology from "Innovation Library" to "Template Library" and refined descriptions for clarity.
src/domain/InnovationPack/admin/AdminInnovationPackPage.tsx Updated error messages and comments to reflect terminology change from "Innovation Pack" to "Template Pack."
src/domain/community/contributor/Account/ContributorAccountView.tsx Modified notification message for deletion from "Innovation Pack deleted successfully!" to "Template Pack deleted successfully!"

Possibly related PRs

Suggested labels

client, enhancement, UX

Suggested reviewers

  • ccano

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.

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.

@DonnaDuiker DonnaDuiker mentioned this pull request Dec 5, 2024
4 tasks
Copy link

@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: 1

🧹 Outside diff range and nitpick comments (1)
src/core/i18n/de/translation.de.json (1)

Line range hint 1815-1817: Update German library section translations

The library section in the German translation needs to be updated to use the new "Template" terminology. Please update the following translations:

-      "fullName": "Best practices",
+      "fullName": "Vorlagenbibliothek",
-      "title": "Innovationsbibliothek auf Alkemio ist hier, um Ihren Weg zu beeinflussen,",
+      "title": "Die Vorlagenbibliothek auf Alkemio ist hier, um Ihren Weg zum Erfolg zu begleiten",
-      "subtitle": "Öffnen Sie die Innovationspakete unten, um alle Whiteboard-Templates, Post-Vorlagen und Innovationsströme, die Sie verwenden können, zu erforschen. Wenn Sie mehr über <click>erfahren möchten, klicken Sie hier</click>.",
+      "subtitle": "Öffnen Sie die Vorlagenpakete unten, um alle Whiteboard-Vorlagen, Post-Vorlagen und Innovationsabläufe zu erkunden, die Sie verwenden können. Wenn Sie mehr darüber <click>erfahren möchten, klicken Sie hier</click>.",
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 727d850 and 4ed8a1f.

⛔ Files ignored due to path filters (1)
  • src/core/apollo/generated/graphql-schema.ts is excluded by !**/generated/**
📒 Files selected for processing (8)
  • src/core/i18n/bg/translation.bg.json (1 hunks)
  • src/core/i18n/de/translation.de.json (1 hunks)
  • src/core/i18n/en/translation.en.json (6 hunks)
  • src/core/i18n/es/translation.es.json (2 hunks)
  • src/core/i18n/fr/translation.fr.json (1 hunks)
  • src/core/i18n/ua/translation.ua.json (2 hunks)
  • src/domain/InnovationPack/admin/AdminInnovationPackPage.tsx (3 hunks)
  • src/domain/community/contributor/Account/ContributorAccountView.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • src/domain/community/contributor/Account/ContributorAccountView.tsx
  • src/core/i18n/en/translation.en.json
🧰 Additional context used
📓 Path-based instructions (6)
src/domain/InnovationPack/admin/AdminInnovationPackPage.tsx (1)

Pattern src/**/*.{ts,tsx,js}: Review the React.js/TypeScript/JavaScript code for best practices and potential bugs.
Ensure that the code adheres to TypeScript's typing system and modern standards.
Use the following code guide documentation in the codebase: 'docs/code-guidelines.md'.

Ensure sufficient error handling and logging is present, but note:

  • Local try/catch blocks are not required unless they provide value
    beyond what the global error handler already covers.
  • Avoid flagging the absence of local error handling in cases where the
    global error handler suffices.
  • Avoid flagging the absence of logging in cases where the global logger is
    already in place (graphql usage).

Inform about the recommendation of not using non-null assertion,
except on GraphQL queries where the variable is asserted non-null and followed by a
skip: with the same variable.
Examples:

  • Not Required: there's a skip
    {
    variables: { templateId: templateId! },
    skip: !templateId,
    }

Check for common security vulnerabilities such as:

  • SQL Injection
  • XSS (Cross-Site Scripting)
  • CSRF (Cross-Site Request Forgery)
  • Insecure dependencies
  • Sensitive data exposure
src/core/i18n/de/translation.de.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/ua/translation.ua.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/fr/translation.fr.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/bg/translation.bg.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

src/core/i18n/es/translation.es.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

🔇 Additional comments (9)
src/domain/InnovationPack/admin/AdminInnovationPackPage.tsx (3)

51-51: LGTM! Error message updated correctly.

The error message has been updated to use "Template Pack" consistently with the PR objectives.


61-61: LGTM! Error message updated correctly.

The error message has been updated to use "Template pack" consistently with the PR objectives.


135-135: LGTM! Comment updated correctly.

The comment has been updated to use "Template pack" consistently with the PR objectives.

src/core/i18n/bg/translation.bg.json (1)

2325-2327: LGTM! Translation strings updated correctly.

The translation strings have been updated to use "Template" terminology consistently with the PR objectives.

src/core/i18n/ua/translation.ua.json (2)

1815-1816: LGTM! Translation strings updated correctly.

The translation strings have been updated to use "Template Library" consistently with the PR objectives.


2325-2327: LGTM! Translation strings updated correctly.

The translation strings have been updated to use "Template" terminology consistently with the PR objectives.

src/core/i18n/es/translation.es.json (2)

1815-1817: LGTM! Library terminology changes are consistent

The renaming from "Innovation library" to "Template library" has been correctly implemented in the Spanish translation file. The changes maintain consistency with the English terminology while preserving the meaning in Spanish.


2325-2327: LGTM! Home section library references updated correctly

The library references in the home section have been properly updated to use "Template" terminology instead of "Innovation". The translations are consistent with the overall terminology changes.

src/core/i18n/fr/translation.fr.json (1)

2325-2327: LGTM! The terminology changes are consistent.

The renaming from "Innovation library/packs" to "Template library/packs" has been properly implemented in the French translation file.

src/core/i18n/de/translation.de.json Show resolved Hide resolved
Copy link
Contributor

@ccanos ccanos left a comment

Choose a reason for hiding this comment

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

Sorry we can't merge this, will call you later and fix it with you

src/core/apollo/generated/graphql-schema.ts Outdated Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

Only the messages in the English file should be updated, the rest of languages should be changed in crowdin, will call you and show you how @DonnaDuiker

@ccanos
Copy link
Contributor

ccanos commented Dec 5, 2024

Closing it as per our conversation

@ccanos ccanos closed this Dec 5, 2024
@SimoneZaza SimoneZaza linked an issue Dec 6, 2024 that may be closed by this pull request
4 tasks
@DonnaDuiker DonnaDuiker removed a link to an issue Dec 13, 2024
4 tasks
@ccanos ccanos deleted the Product_team_updates branch January 30, 2025 10:10
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