-
Notifications
You must be signed in to change notification settings - Fork 13
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
Option to prefer xcproject over xcworkspace (for schemes) #89
Comments
Oh yeah this is a great idea! Maybe it makes the most sense to open up some kind of If you have the time and want to take this on, I'd love to see a PR and would be more than happy to review/merge it! |
I think this matches the current way of configuring the project well. I'd like to add g:xcode_ignore_pods where the workspace schemes subtracting Pods/Pods.xcodeproj schemes would be shown. What do you think of this option? I would suggest a default value of 0 to not change the current default behavior. |
I think I'd like to avoid building in any CocoaPods specific knowledge here, honestly. Maybe a compromise would be like let g:xcode_scheme_source_ignore = [
\ "Pods/Pods.xcodeproj"
\ ] or whatever to filter out any cocoapods sources from any of your projects? |
Love the ignore idea. |
I've added the What do you think of |
I've written a small plugin to source vim-files depending on the current project. |
When using Cocoapods you have a workspace where all the schemes of the pods and your own schemes exist.
Most of the time you don't want to run the pods schemes but only your own.
I would like to have an option to ignore the workspace for the list of your schemes.
If you don't like this option another way to fix this would be to look for Pods.xcodeproj and substract these schemes.
I'd try to implement this myself, if you'd be open to merge it 👍
The text was updated successfully, but these errors were encountered: