Sam Deane
You could still have a manifest flag for ultimate control. I was just thinking that the default of running all Xcode projects might reduce the number of interventions required. I...
As a first stab are you imagining an additional icon on the information page for a package - in this area? (assuming that we're talking about just a "binary only"...
I've done the UI changes required for this, but still need to do the code to actually feed into whether the package is binary-only. Am I right in thinking that...
> We could grab all the target information and store it in a JSON field To do this, I think we'd have to extend `Manifest.Target`'s definition to fully match SPM's...
>> That way we're not over-complicating things now, but there's room for expanding the target info that is stored in the model later, without having to add further fields. >...
I'm happy to give that all a stab. Do you make piecemeal migrations when adding fields, or do you just brute-force rebuild the database since it's all generated anyway?
(I've done Vapor stuff before so I know how that side of things works - ish... ;))
> I'm wrong again! 😁 I’m glad it’s not just me that this happens to (with my own code).
Have switched to the "has binary targets" perspective for now, and updated the names accordingly. I wonder if the wording should be "Some targets in this package do not include...
> @finestructure also had a concern about the cost of pulling in another table to the join, so it may be worth checking the increase in that query cost before...