All 1.3 tn staging

[gouravmore]

Summary by CodeRabbit

• New Features

  • Updated deployment process to trigger from the new branch all-1.3-tn-staging.
  • Restructured content organization by language for better localization in the app.

• Improvements

  • Enhanced error handling and clarity in the VoiceAnalyser component.
  • Improved state management and API interaction in the Practice component.

• Refactor

  • Renamed the Mechanics2 component to Mechanics3 for consistency.
  • Restructured the levelGetContent constant for better maintainability.

• Bug Fixes

  • Adjusted initial state for level in the Practice component to ensure correct processing.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes updates to several components and configuration files. The GitHub Actions workflow file has been modified to change the branch name for deployment triggers. The Mechanics3 component has been renamed from Mechanics2, with added comments for future improvements. The VoiceAnalyser component has received enhancements in error handling and updates to deprecated methods. The constants.js file has been restructured to categorize content by language codes instead of using integer indexing. Lastly, the Practice component has seen changes in state management and error handling improvements.

Changes

File	Change Summary
.github/workflows/all-staging-tn.yml	Updated branch name in on.push.branches from all-1.2-tn-staging to all-1.3-tn-staging.
src/components/Practice/Mechanics3.jsx	Renamed component from Mechanics2 to Mechanics3; updated export statement; added TODO comments.
src/utils/VoiceAnalyser.js	Added error handling in fetchASROutput; refactored getpermision to use navigator.mediaDevices.getUserMedia; clarified comments in handlePercentageForLife.
src/utils/constants.js	Restructured levelGetContent from integer-indexed arrays to an object indexed by language codes.
src/views/Practice/Practice.jsx	Changed initial state of level from "" to 0; updated currentGetContent logic; enhanced error handling in fetchDetails; added TODO comments.

Possibly related PRs

• #0000 updated yml file all-1.2-tn-dev #157: Updates a GitHub Actions workflow file, modifying a workflow configuration file related to deployment processes.
• Issueid #228824 Api integration of Fill in the blanks Mechanics #171: Includes changes to the Mechanics3 component, directly related to the same file in the main PR.
• #0000 audio detection feature enabled #180: Modifies the VoiceAnalyser component, relevant to audio handling in the same context as the main PR.
• Issue #229206 feat: For fill in the blanks mechanic,answer option sho… #187: Involves significant changes to the Mechanics3 component, directly related to updates in the main PR.
• Issueid #0000 iframe height for fill in the blanks #188: Updates the Practice component, relevant for handling game mechanics and audio playback.
• Issueid #0000 iframe height for fill in the blanks #193: Modifies the Practice component, focusing on audio handling and game mechanics, similar to the main PR.
• Issueid #0000 feat: zoom in and out feature enable for fillintheblanks #196: Introduces a zoom feature in the Mechanics3 component, relevant to the same file as the main PR.
• Issueid #0000 feat: zoom in and out feature enable for fillintheblanks #199: Enhances the zoom functionality in the Mechanics3 component, focusing on the same component as the main PR.

---

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

[sonarcloud]

Quality Gate failed

Failed conditions
11.9% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud