Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better UI #2

Closed
neonichu opened this issue Mar 21, 2015 · 3 comments
Closed

Better UI #2

neonichu opened this issue Mar 21, 2015 · 3 comments

Comments

@neonichu
Copy link
Member

Currently, there's way too much boilerplate in the Podfile, it should just be

pod 'Alamofire'

also the command is kinda longish. So ideally, one would do something like:

$ pod bootstrap

and that would amend the Podfile for consumption by the actual pod install and also pass the extra arguments to it.

@neonichu
Copy link
Member Author

Maybe the platform needs to be specified? Would be kinda annoying to first go through all required specs to determine the common denominator of platforms. ¯_(ツ)_/¯

neonichu added a commit that referenced this issue Apr 2, 2015
@neonichu neonichu mentioned this issue Apr 2, 2015
neonichu added a commit that referenced this issue Apr 2, 2015
@AliSoftware
Copy link

Couldn't it be possible to add a pod rome command that internally calls the same ruby code as pod install --no-integrate would do… but tweaking the in-memory ruby representation of the Podfile to add/simulate that use_framework! flag internally?
(Just a thought, didn't check if that's actually possible given CP code architecture)

@segiddins
Copy link
Member

That's totally possible @AliSoftware

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants