-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Add swift language support #2376
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
Comments
Please look at this 3rd party support for Swift, it seems to be usable. https://github.com/ChimeHQ/SwiftTreeSitter, this was listed on Official Tree Sitter website as a 3rd party support. https://tree-sitter.github.io/tree-sitter/ |
To me it looks like Swift support needs to be resolved via Aider-AI/grep-ast#7 |
Please see these two related issues for relevant updates: |
It looks like ast-grep now supports swift, with that and the additions of tree-sitter language pack is swift support now possible in aider? |
Main branch has a big upgrade in programming languages supported by adopting tree-sitter-language-pack.
Including swift. The change is available in the main branch. You can get it by installing the latest version from github:
If you have a chance to try it, let me know if it works for you. |
It's working for me! Thanks! |
I'm closing this enhancement request since it has been marked as 'fixed' for over 3 weeks. The requested feature should now be available in recent versions of aider. If you find that this enhancement is still needed, please feel free to reopen this issue or create a new one. Note: A bot script made these updates to the issue. |
Uh oh!
There was an error while loading. Please reload this page.
Issue
Here are a few resources I've collected. Hopefully they are of some use to you:
tags.scm
in the repo: https://github.com/alex-pinkus/tree-sitter-swift/blob/main/queries/tags.scm.swift-format
is the official lint + format from swiftlang: https://github.com/swiftlang/swift-formatWill this be enough? Thanks.
Version and model info
No response
The text was updated successfully, but these errors were encountered: