@testing-library/react-native 12.2.0 → 12.2.2

package/.github/workflows/main.yml

@@ -1,103 +0,0 @@
-name: Main
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: ['**']
-
-jobs:
-  install-cache-deps:
-    runs-on: ubuntu-latest
-    name: Install and Cache deps
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup
-        uses: ./.github/actions/setup-deps
-
-  lint:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Lint
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Lint
-        run: yarn lint
-
-  typecheck:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Typecheck
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Typecheck
-        run: yarn typecheck
-
-  flow:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Flow
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Flow
-        run: yarn flow
-
-  test:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Test React 18
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Test React 18
-        run: yarn test:ci
-
-      - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v3
-
-  test-react-17:
-    needs: [install-cache-deps]
-    runs-on: ubuntu-latest
-    name: Test React 17
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and deps
-        uses: ./.github/actions/setup-deps
-
-      - name: Test React 17
-        run: yarn test:ci:react:17
-
-  test-website:
-    runs-on: ubuntu-latest
-    name: Test Website
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js and website deps
-        uses: ./.github/actions/setup-website-deps
-
-      - name: Build website
-        run: yarn --cwd website build

package/.gitignore

@@ -1,11 +0,0 @@
-node_modules
-coverage
-*.log
-.eslintcache
-build
-.idea
-.DS_Store
-
-# Ignore lock files in examples for now
-examples/**/yarn.lock
-.docusaurus

package/.prettierrc.js

@@ -1,5 +0,0 @@
-// added for Jest inline snapshots to not use default Prettier config
-module.exports = {
-  singleQuote: true,
-  trailingComma: "es5"
-}

package/CODE_OF_CONDUCT.md

@@ -1,73 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [oss@callstack.io](mailto:oss@callstack.io). All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/
-
-[homepage]: https://www.contributor-covenant.org

package/CONTRIBUTING.md

@@ -1,64 +0,0 @@
-# Contributing
-
-## Code of Conduct
-
-We want this community to be friendly and respectful to each other. Please read [the full text](/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
-
-## Our Development Process
-
-The core team works directly on GitHub and all work is public.
-
-### Development workflow
-
-> **Working on your first pull request?** You can learn how from this _free_ series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
-
-1. Fork the repo and create your branch from `main` (a guide on [how to fork a repository](https://help.github.com/articles/fork-a-repo/)).
-2. Run `yarn` to setup the development environment.
-3. Do the changes you want and test them out in the example app before sending a pull request.
-
-### Commit message convention
-
-We prefix our commit messages with one of the following to signify the kind of change:
-
-- `fix`: bug fixes, e.g. fix incorrect error message.
-- `feat`: new features, e.g. add useful API.
-- `refactor`: code/structure refactor, e.g. new folder structure.
-- `docs`: changes into documentation, e.g. add usage example for `getByText`.
-- `test`: adding or updating tests, eg unit, snapshot testing.
-- `chore`: tooling changes, e.g. change circle ci config.
-- `BREAKING`: for changes that break existing usage, e.g. change API.
-
-Our pre-commit hooks verify that your commit message matches this format when committing.
-
-### Linting and tests
-
-We use `flow` for type checking, `eslint` with `prettier` for linting and formatting the code, and `jest` for testing. Our pre-commit hooks verify that the linter and tests pass when committing. You can also run the following commands manually:
-
-- `yarn flow`: run flow on all files.
-- `yarn lint`: run eslint and prettier.
-- `yarn test`: run tests.
-
-### Sending a pull request
-
-When you're sending a pull request:
-
-- Prefer small pull requests focused on one change.
-- Verify that `flow`, `eslint` and tests are passing.
-- Preview the documentation to make sure it looks good.
-- Follow the pull request template when opening a pull request.
-
-### Publishing a release
-
-If you have publish access to the NPM package, run the following from the main branch to publish a new release:
-
-```sh
-yarn publish
-```
-
-## Reporting issues
-
-You can report issues on our [bug tracker](https://github.com/callstack/react-native-testing-library/issues). Please follow the issue template when opening an issue.
-
-## License
-
-By contributing to `@testing-library/react-native`, you agree that your contributions will be licensed under its **MIT** license.

package/babel.config.js

@@ -1,22 +0,0 @@
-module.exports = {
-  presets: [
-    '@babel/preset-typescript',
-    '@babel/preset-react',
-    [
-      '@babel/preset-env',
-      {
-        targets: {
-          node: '14',
-        },
-        bugfixes: true,
-      },
-    ],
-  ],
-  plugins: ['@babel/plugin-proposal-class-properties'],
-  env: {
-    test: {
-      // https://github.com/react-native-community/upgrade-support/issues/152
-      plugins: ['@babel/plugin-transform-flow-strip-types'],
-    },
-  },
-};

package/build/helpers/filterNodeByType.d.ts

@@ -1,3 +0,0 @@
-import type { ReactTestInstance } from 'react-test-renderer';
-import * as React from 'react';
-export declare const filterNodeByType: (node: ReactTestInstance | React.ReactElement, type: React.ElementType | string) => boolean;

package/build/helpers/filterNodeByType.js

@@ -1,9 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.filterNodeByType = void 0;
-const filterNodeByType = (node, type) => node.type === type;
-exports.filterNodeByType = filterNodeByType;
-//# sourceMappingURL=filterNodeByType.js.map

package/build/helpers/filterNodeByType.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"filterNodeByType.js","names":["filterNodeByType","node","type","exports"],"sources":["../../src/helpers/filterNodeByType.ts"],"sourcesContent":["import type { ReactTestInstance } from 'react-test-renderer';\nimport * as React from 'react';\n\nexport const filterNodeByType = (\n  node: ReactTestInstance | React.ReactElement,\n  type: React.ElementType | string\n) => node.type === type;\n"],"mappings":";;;;;;AAGO,MAAMA,gBAAgB,GAAGA,CAC9BC,IAA4C,EAC5CC,IAAgC,KAC7BD,IAAI,CAACC,IAAI,KAAKA,IAAI;AAACC,OAAA,CAAAH,gBAAA,GAAAA,gBAAA"}