fix: display learning module level regardless of the challenge level

[serapieTuyishime]

Submit a pull request

• This is not a duplicate of an existing pull request.
• No existing features have been broken without good reason.
• Your commit messages are detailed
• The code style guideline have been followed.
• Documentation has been updated to reflect your changes.
• Tests have been added or updated to reflect your changes.
• All tests pass.

---

Replace any ":question:" below with information about your pull request.

Pull Request Details

This PR aims at displaying the learning module level on both; The learning materials and the Challenge pages:question:

Issues Fixed

• Bug: learning module lever not showing on learning materials page #1292
• Bug: learning material showing "0" in place of the duration. #1294

Other Relevant Information

[coderabbitai]

Walkthrough

Walkthrough

The changes involve modifications to the LearningModuleCard and Duration components. The LearningModuleCard now exclusively relies on the data?.level for rendering logic, enhancing its control flow. In the Duration component, the handling of the duration variable has been updated to set it to an empty string when the value prop is falsy, altering its representation from a numeric to a string format.

Changes

File	Change Summary
src/components/cards/LearningModule.tsx	The LearningModuleCard component now uses data?.level exclusively for determining level, and its rendering logic has been adjusted accordingly. The useMemo dependency array has also been updated for performance.
src/components/sections/courses/_partials/Duration.tsx	The Duration component now sets the duration variable to an empty string ("") if the value prop is falsy, changing its representation from numeric to string.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[netlify]

✅ Deploy Preview for staging-dacade ready!

Name	Link
🔨 Latest commit	544b5e3
🔍 Latest deploy log	https://app.netlify.com/sites/staging-dacade/deploys/66cdf0be56e6640008fa28bd
😎 Deploy Preview	https://deploy-preview-1295--staging-dacade.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5947862 and 544b5e3.

Files selected for processing (2)

• src/components/cards/LearningModule.tsx (2 hunks)
• src/components/sections/courses/_partials/Duration.tsx (1 hunks)

Additional comments not posted (3)

src/components/sections/courses/_partials/Duration.tsx (1)

30-30: Verify the impact of the change in duration variable handling.

The duration variable is now set to an empty string when the value prop is falsy. Ensure that this change does not negatively impact any downstream logic or rendering that relies on the duration variable, particularly if it expects a number versus a string.

src/components/cards/LearningModule.tsx (2)

27-29: Verify the impact of the change in level determination.

The level now exclusively relies on data?.level. Ensure that this change does not negatively impact the rendering behavior, particularly in scenarios where the data object might not be available.

---

41-41: Verify the impact of the change in the condition for rendering the Tag component.

The condition for rendering the Tag component has been modified to check for data?.level instead of challenge?.level. Ensure that this change does not negatively impact the rendering behavior, particularly in scenarios where the data object might not be available.