Tyler Thompson

Nothing quite so simple I’m afraid. I didn’t screenshot it well but I did document that if I simply run `git status` my prompt becomes aware of what’s up. to...

Some notes: I've run the entire test suite 1000 times to look for any flakes and what's there as of the time of writing is solid. The `ComposedGestureExampleTests` seemed to...

Another note. Previously the view hosting and inspection code really sort of made an assumption that each inspection would be set up *before* the callbacks would happen. A straight translation...

`onReceive` poses its own challenges. As we move into structured concurrency the issue is that a publisher might fire off before there is a subscription. I've currently "worked around" this...

Glad you got a chance to look at it! I'll see what progress I can make today. The PR is likely to get a bit more noisy in terms of...

So running tests on watchOS had some build issues which I fixed and some runtime fatalErrors which I haven't. Thing is, the same is true in the trunk branch. I'm...

> @Tyler-Keith-Thompson are you using the `.watchOS/watchOS.xcodeproj` for watchOS tests? You're right! I missed that. watchOS works fine.

@nalexn So I spent quite a bit of time looking at this: https://github.com/nalexn/ViewInspector/pull/291#issuecomment-1962897099 Your proposed API has a couple problems. The first is it'd require a very clever custom ResultBuilder...

My note on backward compatibility. So the biggest "breaking" change we've made here is that inspection closures must be Sendable now. Practically speaking if consumers follow the normative examples you...

Alright, I've addressed all comments (thank you everybody for the reviews!) If it all makes sense I think we're ready to rock on this PR. I'm happy to tweak it...