Brentley Jones

@BalestraPatrick I think 727681df4f91e2e2f38c35f78cea9f6f001430e3 actually fixed this, since the first bullet above no longer applies. We might still have issues because of the off-by-one "this target is green, everything is...

Probably a relative path issue, similar to the Test Issue navigation that we fixed. I wonder if there is something we can swizzle here to fix this in the same...

I believe @chiragramani looked into this and it doesn't look easy to fix. Care to share your findings @chiragramani?

I don't believe this should block 1.0.

> This allows integrating linting/formatting tools into your Xcode project to get warnings and errors displayed in the issue navigator. > > Unlike pre/post actions, additional build phases don't belong...

>I'm assuming this use case won't work in a pre-scheme action, but I admit I've never tried either. I believe Xcode still doesn't render the output from scheme pre-build actions,...

Seems I'll need to find a way to escape some paths in tool invocations, and if not possible give up ☹️. Though it looks like it works in Bazel 6.0,...

Unit files have a hash based on the object file path. When we import unit files we need to make the object file path equal to what it would be...

And after saying all of that, I think I'll add something to index-import to address this for the time being.

https://github.com/MobileNativeFoundation/index-import/pull/65 We can merge this PR once we drop Bazel 5.x support.