Skip to content

Support for choosing framework search paths in flycheck. #90

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

Merged
merged 1 commit into from
Mar 27, 2015

Conversation

nathankot
Copy link
Contributor

Especially useful when using Carthage as a package manager, can just point it to
Carthage/Build/iOS

@@ -583,11 +583,15 @@
(string :tag "Linked Sources"))
:safe #'stringp)

(flycheck-def-option-var flycheck-swift-framework-search-paths nil swift
"A list of framework search paths")

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be worth adding a sanity check here with :safe #'flycheck-string-list-p, what do you think?

@nathankot
Copy link
Contributor Author

@ap4y good spotting!

@ap4y
Copy link
Collaborator

ap4y commented Mar 27, 2015

Thanks @nathankot, can I ask you to squash this commits into one? Will help keeping history clean on master.

@nathankot nathankot force-pushed the flycheck-framework-search-paths branch from c2ca5e1 to 68a3a29 Compare March 27, 2015 03:27
@nathankot
Copy link
Contributor Author

@ap4y done :)

ap4y added a commit that referenced this pull request Mar 27, 2015
Support for choosing framework search paths in flycheck.
@ap4y ap4y merged commit dbf48a1 into swift-emacs:master Mar 27, 2015
@ap4y
Copy link
Collaborator

ap4y commented Mar 27, 2015

Thanks @nathankot!

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

Successfully merging this pull request may close these issues.

2 participants