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

Fix: Migrated Mocks directory into Scripts directory #1650

Conversation

akhilender-bongirwar
Copy link
Contributor

What kind of change does this PR introduce?
This PR makes sure the __mocks__ directory is relocated to scripts/ directory.

Issue Number:

Fixes #1391

Summary

  • The __mocks__ directory is used for testing the Avatar component and may also serve as a location for testing future libraries, such as dicebear, where Jest encounters errors due to its inability to handle non-standard syntax.
  • Ensured that no tests were adversely affected by the modifications.

Does this PR introduce a breaking change?
No

Other information

Have you read the contributing guide?
Yes

- Ensured no test got affected with the modified changes.

Signed-off-by: Akhilender <[email protected]>
Copy link

github-actions bot commented Mar 2, 2024

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

codecov bot commented Mar 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.61%. Comparing base (3601c92) to head (b3286dc).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1650   +/-   ##
========================================
  Coverage    97.61%   97.61%           
========================================
  Files          157      157           
  Lines         3991     3991           
  Branches      1201     1201           
========================================
  Hits          3896     3896           
- Misses          89       90    +1     
+ Partials         6        5    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@akhilender-bongirwar
Copy link
Contributor Author

This is slight modification of PR #1585.

@palisadoes palisadoes merged commit 6982c09 into PalisadoesFoundation:develop Mar 2, 2024
10 of 12 checks passed
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