Skip to content

feat: improve, document module testability #587

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

Merged
merged 7 commits into from
Jul 27, 2022
Merged

Conversation

vonovak
Copy link
Member

@vonovak vonovak commented Mar 27, 2022

Summary

closes #510
closes #216
closes #637

There are still some improvements to be made but those will involve some changes to the api of the package.

Test Plan

What's required for testing (prerequisites)?

What are the steps to reproduce (after prerequisites)?

Compatibility

OS Implemented
iOS
Android

Checklist

  • I have tested this on a device and a simulator
  • I added the documentation in README.md
  • I updated the typed files (TS and Flow)
  • I added a sample use of the API in the example project (example/App.js)
  • I have added automated tests, either in JS or e2e tests, as applicable

@vonovak vonovak changed the title feat: prep for improving module testability feat: improve module testability Mar 27, 2022
@vonovak vonovak changed the title feat: improve module testability feat: improve, document module testability Mar 27, 2022
@vonovak vonovak force-pushed the feat/testing-guide branch from 0497d0d to 2be2b35 Compare July 27, 2022 15:34
@vonovak vonovak marked this pull request as ready for review July 27, 2022 15:48
@vonovak vonovak enabled auto-merge (squash) July 27, 2022 15:48
@vonovak vonovak merged commit 9e27cb1 into master Jul 27, 2022
@vonovak vonovak deleted the feat/testing-guide branch July 27, 2022 16:00
vonovak pushed a commit that referenced this pull request Jul 27, 2022
# [6.3.0](v6.2.2...v6.3.0) (2022-07-27)

### Features

* improve, document module testability ([#587](#587)) ([9e27cb1](9e27cb1))
@vonovak
Copy link
Member Author

vonovak commented Jul 27, 2022

🎉 This issue has been resolved in version 6.3.0 🎉

If this package helps you, consider sponsoring us! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant