chore: Scaffold jest mock project. #483
Conversation
yusinto
changed the title
| @@ -0,0 +1,3 @@ | |||
| # Changelog | |||
|
|
|||
| All notable changes to the LaunchDarkly Jest package will be documented in this file. This project adheres to [Semantic Versioning](https://semver.org). | |||
There was a problem hiding this comment.
Is this a continuation of the existing library?
There was a problem hiding this comment.
No it's not. It will be a new library published under @launchdarkly/jest and initially only supports react-native mocks. Subsequently it should only support mocks for new major versions of the react and js sdks under js-core.
Co-authored-by: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>
| # HACK: jest is not ready for release yet. | ||
| if: false #${{ needs.release-please.outputs.package-tooling-jest-release == 'true' }} |
There was a problem hiding this comment.
@kinyoklion this should stop auto-release. Manual publish is still active, but I think that's ok?
There was a problem hiding this comment.
This will prevent publishing packages, but will still make release PRs with changelog entries and things. Which is fine so long as you are ok with the tags and things.
There was a problem hiding this comment.
Ok ta. I've also rolled back release-please-config.json.
As part of the mentorship program, @professorice and I have been working on the react-native mock library. This PR is to scaffold the jest mock library in js-core, so we can work on the react-native mock library and also other jest mocks in the future.
# The new jest package lives here packages/tooling/jest