feat: Refactor example screen

[himanshu-wedensday]

Ticket Link

---

Related Links

---

Description

---

Steps to Reproduce / Test

---

GIF's

---

Summary by CodeRabbit

• Refactor
  • Enhanced ExampleScreen by transitioning it from a class to a functional component, improving data fetching with modern React hooks.
• Tests
  • Improved the testing framework for ExampleScreen with better setup functions and streamlined state mocking in test cases.

[coderabbitai]

Walkthrough

The recent updates involve transforming the ExampleScreen from a class component to a more modern functional component with hooks, enhancing data fetching with useEffect. Additionally, the testing environment across various files has been fortified with new setups and refactoring to streamline the mock and state management, ensuring more robust and maintainable tests.

Changes

Files	Changes
app/.../ExampleScreen/index.js, app/.../ExampleScreen/saga.js	Refactored to functional component using hooks, updated lodash import, and improved data fetching method.
app/.../ExampleScreen/tests/index.test.js, app/.../ExampleScreen/tests/reducer.test.js, app/.../ExampleScreen/tests/selectors.test.js	Enhanced testing setup with new mock and state management functions, and streamlined test cases.

🐰✨
Oh hark! A refactor bright,
With hooks and tests that might,
Make our code so light and free,
A functional shift, a sight to see!
Cheers to clean code, hip hooray! 🎉

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between efa2b17 and d7d41b1.

Files selected for processing (5)

• app/scenes/ExampleScreen/index.js (2 hunks)
• app/scenes/ExampleScreen/saga.js (1 hunks)
• app/scenes/ExampleScreen/tests/index.test.js (2 hunks)
• app/scenes/ExampleScreen/tests/reducer.test.js (1 hunks)
• app/scenes/ExampleScreen/tests/selectors.test.js (1 hunks)

Files skipped from review due to trivial changes (1)

• app/scenes/ExampleScreen/saga.js

Additional comments not posted (7)

app/scenes/ExampleScreen/tests/selectors.test.js (2)

8-16: The introduction of setupMockedState function enhances the readability and maintainability of the test setup.

---

27-41: Refactoring test cases to use setupMockedState ensures consistency and reduces redundancy. Good job on enhancing the test structure.

app/scenes/ExampleScreen/tests/index.test.js (2)

10-10: Introduction of setupJest function centralizes Jest mock setup, enhancing consistency and reusability in tests.

---

7-29: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [13-36]

Refactoring test cases to use setupJest for setting up mocks ensures consistency and reduces redundancy. Well done on improving the test structure.

app/scenes/ExampleScreen/tests/reducer.test.js (2)

8-11: Introduction of setupState function centralizes state setup, enhancing consistency and reusability in reducer tests.

---

14-54: Refactoring test cases to use setupState for setting up state ensures consistency and reduces redundancy. Excellent work on improving the test structure.

app/scenes/ExampleScreen/index.js (1)

47-72: Refactoring ExampleScreen to a functional component using hooks aligns with modern React best practices. The use of useEffect for side effects and defining requestFetchUser within the component enhances readability and maintainability.

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

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

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	95.17% (+0.02% 🔼)	197/207
🟢	Branches	87.8%	36/41
🟢	Functions	93.51% (-0.08% 🔻)	72/77
🟢	Lines	96.13% (+0.04% 🔼)	174/181

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / index.js	86.67% (+0.95% 🔼)	100%	60% (-6.67% 🔻)	92.86% (+1.19% 🔼)

Test suite run success

52 tests passing in 24 suites.

Report generated by 🧪jest coverage report action from d7d41b1

[sonarqube-ws]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• 100.00% Coverage (94.60% Estimated after merge)
• 0.00% Duplicated Code (0.00% Estimated after merge)

Project ID: wednesday-solutions_react-native-template_AY7hdnRSB2n8RRmGoU2M

View in SonarQube