[tonytonycoder11]

Five milestones of 0.2.0 in one branch, so that CI runs once: calls from other isolates (M19), comparing two calls (M17), statistics and a timeline (M20), dock mode (M21) and mocks and breakpoints (M18). Each has its own commit, in that order. Four more follow: one from a review of the whole branch, two from running the example on an Android emulator, and one line of documentation.

Calls from other isolates. Overrides belong to one isolate, so a call made with Isolate.run or compute was never seen. Flutwire.run and Flutwire.compute stand in for them, and an isolate you start yourself calls Flutwire.attach(). The isolate records its own calls with the redaction and the size limit of the app and sends each snapshot over a named port to the main isolate, which puts the call in the history under an id of its own, because two isolates can number their calls the same.

Comparing two calls. Select two calls and the compare button opens them side by side: the overview, the query, the header fields and the bodies, with what differs marked. Text is compared by line with Myers' algorithm, bounded to 1500 edits so that two bodies with nothing in common cost a bounded amount of work. JSON and XML are laid out first, so a change of indentation is not a difference, a form is compared field by field, and anything else as bytes.

Statistics and a timeline. A summary gives the counts, the error rate, the average, the median and the 95th percentile, the ten slowest calls and the hosts ranked by how often they fail. The timeline lays the latest hundred calls on one line, with the wait for the first byte apart from the answer coming in, and counts how many were in flight at once. A WebSocket, an event stream and a call held at a breakpoint count as calls but take no part in the times.

Dock mode. Flutwire.builder lays the app and the inspector out in one row or column, so the inspector sits beside the app on a wide screen and under it on a phone. The app is always the first child of the same flex, so docking never rebuilds it and it keeps its state, and it sees the smaller screen through its own MediaQuery. The panel has a navigator of its own, so Back stays inside it, the strip between the two resizes it, and the side and the size are kept.

Mocks and breakpoints. FlutwireConfig.interception is off by default, because this is the first thing Flutwire does that changes traffic. A rule matches the address of a request, with * for any run of characters, and optionally its method, and the newest enabled rule that matches wins. A mock answers with a stored response and never opens a connection. A breakpoint holds the request when the app closes it, opens it in the editor used for sending a call again, and sends it on as it was, sends it changed as a call that repeats the original, or stops it so that the app's call fails. Switching a breakpoint off or deleting it sends on what it holds, because a wide rule could otherwise be undone only one request at a time. It works through the dart:io capture, so it does nothing on the web, and a call made in another isolate is recorded but never mocked or held. The held editor shows the real header fields, authorization included, because the request has not been recorded yet.

What the review found, and fixed. Sending or stopping a held request while another one waited closed the next request's editor and left its own on screen, because the page popped whatever was on top. A second abort of a mocked request threw. The recorder's interception hooks were public on an exported class and are internal now. The text writes of a request, the way a body is edited, the bar at the foot of an editor and the routes to a call, a comparison and the rules were each written twice or three times, and a few members were used by tests only.

What the emulator found, and fixed. After a request had been held for a while the average and the percentiles went to minutes, because a held call lasts as long as somebody looked at it. A history kept from earlier runs squeezed the timeline into a corner and ran the labels of its axis together, so it now starts after the latest pause of two minutes. The Save button of the rule editor had shrunk to its text since the bottom bar was shared, and a rule's address was cut before its path.

Checked. The flutwire suite has 1112 tests and the three adapters 15, 12 and 19, all passing, and flutter analyze --fatal-infos and the format check are clean. I ran the other CI jobs locally: the four flutter pub publish --dry-runs, the lowest versions of each package, and the example for Android, the iOS simulator, macOS and the web. On an Android emulator I made a mock and a breakpoint from a call, watched the inspector come forward over the app when a request was held, sent it on changed and as it was, switched the breakpoint off with a request held, docked the inspector, compared two calls, opened the statistics and ran a call through Flutwire.run.

Not checked. Only Android was run. iOS, macOS and the web were built and not run, and none of this touches native code. The Protobuf decoder has still not met a descriptor set from a real protoc. A mock made from a call serves the placeholder where the redaction masked a value, which the editor shows but does not flag.

Targets 0.2.0, Tier 2, M17 to M21.

[trueup-by-nacode-studios]

This pull request adds no capability the code did not already have.

_{68 files read · 3607 ms · against 8b56bbc · engine 1.4.1}