dependabot[bot] 27e7cf2804 Bump mockito-core from 4.9.0 to 5.0.0 (#4444)
Summary:
Bumps [mockito-core](https://github.com/mockito/mockito) from 4.9.0 to 5.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/mockito/mockito/releases">mockito-core's releases</a>.</em></p>
<blockquote>
<h2>v5.0.0</h2>
<h1>Mockito 5: prepare for future JDK versions</h1>
<p>For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.</p>
<h2>Switch the default mockmaker to <code>mockito-inline</code></h2>
<p>Back in Mockito 2.7.6, we published a new mockmaker based on the &quot;inline bytecode&quot; principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates &quot;real&quot; subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.</p>
<p>Massive thanks to community member <a href="https://github.com/reta"><code>@​reta</code></a> who implemented this change.</p>
<h3>When should I still be using the subclass mockmaker?</h3>
<p>There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.</p>
<p>If you want to use the subclass mockmaker instead, you can use the new <code>mockito-subclass</code> artifact (published <a href="https://search.maven.org/artifact/org.mockito/mockito-subclass">on Maven Central</a> along with all our other artifacts).</p>
<h2>Update the minimum supported Java version to 11</h2>
<p>Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes <a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2798">issues with the <code>SecurityManager</code></a>.
Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.</p>
<p>Massive thanks to community member <a href="https://github.com/reta"><code>@​reta</code></a> who implemented this change.</p>
<h3>What should I do if I still run JDK 8?</h3>
<p>For JDK 8 and below, you can keep on using Mockito 4.
This is similar to if you are using JDK 6, for which you can keep on using Mockito 2.
The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal.
However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.</p>
<h2>New <code>type()</code> method on <code>ArgumentMatcher</code></h2>
<p>One of our most used public API's for customizing Mockito is the <a href="https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/ArgumentMatcher.html"><code>ArgumentMatcher</code> interface</a>.
The interface allows you to define a custom matcher, which you can pass into method arguments to provide more targeted matches.
One major shortcoming of the <code>ArgumentMatcher</code> was the lack of varargs support.</p>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="adf528d173"><code>adf528d</code></a> Bump versions.bytebuddy from 1.12.21 to 1.12.22 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2864">https://github.com/facebook/flipper/issues/2864</a>)</li>
<li><a href="2418419a19"><code>2418419</code></a> Bump versions.junitJupiter from 5.9.1 to 5.9.2 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2858">https://github.com/facebook/flipper/issues/2858</a>)</li>
<li><a href="3d40cd51d3"><code>3d40cd5</code></a> Bump junit-platform-launcher from 1.9.1 to 1.9.2 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2859">https://github.com/facebook/flipper/issues/2859</a>)</li>
<li><a href="9bec8e3a1a"><code>9bec8e3</code></a> Bump versions.errorprone from 2.17.0 to 2.18.0 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2857">https://github.com/facebook/flipper/issues/2857</a>)</li>
<li><a href="a9595f559c"><code>a9595f5</code></a> Switch the default mockmaker to the inline mockmaker on JDK 17+ (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2834">https://github.com/facebook/flipper/issues/2834</a>)</li>
<li><a href="c5d7fbc532"><code>c5d7fbc</code></a> Bump assertj-core from 3.23.1 to 3.24.1 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2854">https://github.com/facebook/flipper/issues/2854</a>)</li>
<li><a href="dbd7f2ff4a"><code>dbd7f2f</code></a> Bump versions.bytebuddy from 1.12.20 to 1.12.21 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2852">https://github.com/facebook/flipper/issues/2852</a>)</li>
<li><a href="4d62fa75c7"><code>4d62fa7</code></a> Bump junit from 1.1.4 to 1.1.5 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2850">https://github.com/facebook/flipper/issues/2850</a>)</li>
<li><a href="b1b6d6afcb"><code>b1b6d6a</code></a> Bump espresso-core from 3.5.0 to 3.5.1 (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2849">https://github.com/facebook/flipper/issues/2849</a>)</li>
<li><a href="7b5b8dd840"><code>7b5b8dd</code></a> Remove use case for non-existent method VerificationWithTimeout#never (<a href="https://github-redirect.dependabot.com/mockito/mockito/issues/2848">https://github.com/facebook/flipper/issues/2848</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/mockito/mockito/compare/v4.9.0...v5.0.0">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.mockito:mockito-core&package-manager=gradle&previous-version=4.9.0&new-version=5.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

 ---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `dependabot rebase` will rebase this PR
- `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `dependabot merge` will merge this PR after your CI passes on it
- `dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `dependabot cancel merge` will cancel a previously requested merge and block automerging
- `dependabot reopen` will reopen this PR if it is closed
- `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Pull Request resolved: https://github.com/facebook/flipper/pull/4444

Reviewed By: antonk52

Differential Revision: D42678087

Pulled By: passy

fbshipit-source-id: 7e1e38af900b985a26b42342297e15ab7eda9546
2023-01-24 06:39:36 -08:00
2023-01-20 10:19:06 -08:00
2023-01-20 10:19:06 -08:00
2023-01-18 01:41:10 -08:00
2023-01-10 06:14:43 -08:00
2020-07-08 07:10:46 -07:00
2020-11-09 08:24:28 -08:00
2020-03-26 05:53:53 -07:00
2022-09-12 03:48:43 -07:00
2019-09-30 06:41:57 -07:00
2018-06-01 11:03:58 +01:00
2020-04-14 09:21:58 -07:00
2018-07-31 08:15:12 -07:00
2019-08-29 23:21:14 -07:00
2020-11-09 08:24:28 -08:00
2022-02-16 08:22:09 -08:00
2022-02-16 08:22:09 -08:00
2022-12-05 07:57:16 -08:00
2022-02-25 02:33:22 -08:00
2020-08-10 08:47:32 -07:00

logo

Flipper

Android Maven Badge iOS

Flipper (formerly Sonar) is a platform for debugging mobile apps on iOS and Android and JS apps in your browser or in Node.js. Visualize, inspect, and control your apps from a simple desktop interface. Use Flipper as is or extend it using the plugin API.

Flipper

Table of Contents

Mobile development

Flipper aims to be your number one companion for mobile app development on iOS and Android. Therefore, we provide a bunch of useful tools, including a log viewer, interactive layout inspector, and network inspector.

Extending Flipper

Flipper is built as a platform. In addition to using the tools already included, you can create your own plugins to visualize and debug data from your mobile apps. Flipper takes care of sending data back and forth, calling functions, and listening for events on the mobile app.

Contributing to Flipper

Both Flipper's desktop app, native mobile SDKs, JS SDKs are open-source and MIT licensed. This enables you to see and understand how we are building plugins, and of course, join the community and help to improve Flipper. We are excited to see what you will build on this platform.

In this repo

This repository includes all parts of Flipper. This includes:

  • Flipper's desktop app built using Electron (/desktop)
  • native Flipper SDKs for iOS (/iOS)
  • native Flipper SDKs for Android (/android)
  • React Native Flipper SDK (/react-native)
  • JS Flipper SDK (/js)
  • Plugins:
    • Logs (/desktop/plugins/public/logs)
    • Layout inspector (/desktop/plugins/public/layout)
    • Network inspector (/desktop/plugins/public/network)
    • Shared Preferences/NSUserDefaults inspector (/desktop/plugins/public/shared_preferences)
  • website and documentation (/website / /docs)

Getting started

Please refer to our Getting Started guide to set up Flipper. Or, (still experimental) run npx flipper-server for a browser based version of Flipper.

Requirements

  • node >= 8
  • yarn >= 1.5
  • iOS developer tools (for developing iOS plugins)
  • Android SDK and adb

Building from Source

Desktop

Running from source

git clone https://github.com/facebook/flipper.git
cd flipper/desktop
yarn
yarn start

NOTE: If you're on Windows, you need to use Yarn 1.5.1 until this issue is resolved.

Building standalone application

Provide either --mac, --win, --linux or any combination of them to yarn build to build a release zip file for the given platform(s). E.g.

yarn build --mac --version $buildNumber

You can find the resulting artifact in the dist/ folder.

iOS SDK + Sample App

cd iOS/Sample
rm -f Podfile.lock
pod install --repo-update
open Sample.xcworkspace
<Run app from xcode>

You can omit --repo-update to speed up the installation, but watch out as you may be building against outdated dependencies.

Android SDK + Sample app

Start up an android emulator and run the following in the project root:

./gradlew :sample:installDebug

React Native SDK + Sample app

Requires RN 0.69+!

cd react-native/ReactNativeFlipperExample
yarn
yarn android

Note that the first 2 steps need to be done only once.

Alternatively, the app can be started on iOS by running yarn ios.

If this is the first time running, you will also need to run pod install --repo-update from the react-native/ReactNativeFlipperExample/ios folder.

React Native Windows (Experimental)

An experimental version of Flipper for React Native Windows is available. The following steps prepare the React Native Flipper project:

cd react-native/react-native-flipper
vcpkg install openssl:x64-uwp openssl:arm-uwp
vcpkg integrate install
yarn install
cd windows
nuget install ReactNativeFlipper/packages.config

In a nutshell, vcpkg is used to install OpenSSL. Nuget is used to install Boost.

Then, the sample application can be built and run as follows:

cd ../../ReactNativeFlipperExample
yarn install
yarn relative-deps
npx react-native run-windows

At the moment there's no available package for React Native Flipper. This means that to integrate Flipper with any other existing applications, an explicit reference to the project needs to be added just as is done with the sample application.

JS SDK + Sample React app

cd js/react-flipper-example
yarn
yarn start

Troubleshooting

Older yarn versions might show an error / hang with the message 'Waiting for the other yarn instance to finish'. If that happens, run the command yarn first separately in the directory react-native/react-native-flipper.

Documentation

Find the full documentation for this project at fbflipper.com.

Our documentation is built with Docusaurus. You can build it locally by running this:

cd website
yarn
yarn start

Contributing

See the CONTRIBUTING file for how to help out.

License

Flipper is MIT licensed, as found in the LICENSE file.

Description
No description provided
Readme 106 MiB
Languages
TypeScript 61.2%
Java 9.9%
Objective-C 7%
Kotlin 5.8%
C++ 4.8%
Other 11.2%