-
Notifications
You must be signed in to change notification settings - Fork 282
Support showing an overview of the integration #77
Comments
the ... is meant to be and more, not to crop |
This is now possible with #103 merged - see |
Alright, so, my shopping list:
Podfile wide info
Targets
Target's Pods
|
Do you need all of these at the same time? Or can there be subset queries and, if so, what would those be? |
Actually, the Podfile stuff is fine in 1 query, but the xcodeproj ones would probably be nice to subquery, so if those are in another view, that would be nice. |
This is aiming for 1 tableview style stuff, so it's probably not going to dig in much further here. A bunch of the xcodeproj introspection stuff is probably above the fold visuals, can do async but ideally not. |
Otherwise things like Target's pods, are a pretty low priority, but I bet those are easy gets given they're in |
depending on how it works out in implementation time, I can think about ways to fix with design if xcodeproj stuff is timely and we need to re-think, otherwise it's more or less everything upfront |
So far I have this data (extracted from Eigen’s Podfile):
|
ouch, that's good that! |
:) Is the only important thing missing atm the deployment target of each target? |
Yeah, I think that's enough to show what we want. |
This is in |
Shows each target, ideally taking the app icon from the Target's info.plist ( and having some known ones otherwise, I can provide these. )
For the simplest v1, lets just show a link to the website and the current version. Definitely things we can build on from there.
Blocked by #76
The text was updated successfully, but these errors were encountered: