-
Notifications
You must be signed in to change notification settings - Fork 623
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
Feature Request: Use companion app to configure option not use by the Xcode extension #375
Comments
This makes sense. I do wonder how we can make it clear that the options in the "options" tab have no effect on the Xcode extension however. There is already confusion for some users about why the Xcode extension doesn't auto-detect .swiftformat files exported from the app and placed in the project folder, so I'd prefer not to deepen that confusion if possible. |
@nicklockwood that is a valid point, I have a new colleague that thought that the companion app was also configuring the command line app. Maybe if the tab was call "Command Line" and that a message in read at the top of the tab with a short description stating something like: "To use the configuration, save the file and use the following swiftformat command: 'swiftformat /.../' " |
Currently the configuration file produce by the Swift Format for Xcode application only include options and rules that can be apply in the Xcode code extension. However, the file can be use as an input to the swiftformat command line application.
In order to better support the sharing of configuration file between the Xcode extension and the command line application it would be interesting to see a "tab" in the Swift Format for Xcode application that would display rules and options only use by the command line application.
The text was updated successfully, but these errors were encountered: