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

sourcekitten 0.2.4 #124

Merged
merged 2 commits into from
Dec 25, 2014
Merged

sourcekitten 0.2.4 #124

merged 2 commits into from
Dec 25, 2014

Conversation

jpsim
Copy link
Collaborator

@jpsim jpsim commented Dec 23, 2014

This version of sourcekitten logs to STDERR when it can't parse a Swift file (see jpsim/SourceKitten@964581c). This will hopefully help debug and encourage people to file an issue with sufficient information when there's something wrong.

@segiddins
Copy link
Collaborator

JP ideally this info would be passed along in a structured manner to jazzy

@jpsim
Copy link
Collaborator Author

jpsim commented Dec 23, 2014

@segiddins ideally, jazzy would build sourcekitten from source. I believe ruby calls these "native extensions"?

@segiddins
Copy link
Collaborator

JP yes, but that's a different issue. I'm saying instead of logging only to STDERR, also include errors in the structured sourcekitten output.

@jpsim
Copy link
Collaborator Author

jpsim commented Dec 23, 2014

Ah, gotcha. That would be easy enough to do just by logging JSON with error info to STDOUT at the same time. I created jpsim/SourceKitten#16 to track that.

@segiddins
Copy link
Collaborator

Ace.

@jpsim
Copy link
Collaborator Author

jpsim commented Dec 25, 2014

Now using sourcekitten 0.2.5 & safer write_undocumented_file.

jpsim added a commit that referenced this pull request Dec 25, 2014
sourcekitten 0.2.5 and safer write_undocumented_file
@jpsim jpsim merged commit ef8110c into master Dec 25, 2014
@jpsim jpsim deleted the jp-sourcekitten-0.2.4 branch December 25, 2014 01:38
@pigeondotdev pigeondotdev modified the milestone: The Past Nov 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants