You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I wanted to "filter" some tags while using xcdiff, I used xcdiff --list to print the tags. I removed 2 of them, and, to my surprise, diffing jumped from a few seconds to around 30.
I messaged @kwridan in the Tuist Slack, and he pointed me to this file: Comparators.md. Kas explained (as written in the mentioned md file) that the RESOLVED_SETTINGS tag depends on xcodebuild under the hood, and this is why this tag is disabled by default.
Ideally, listing the tags should inform the user which tags are enabled/disabled by default, so mimicking the default behavior is easier.
An example of this is the SwiftLint's rules command, which prints much more information:
For xcdiff, a table with the tags, description, and enabled by default would be even better.
The text was updated successfully, but these errors were encountered:
…default (#55)
Resolves#49
Test Plan:
- CI
- Run `xcdiff --list`, ensure all except `RESOLVED_SETTINGS` comparators are listed with default value `Yes`.
Signed-off-by: Marcin Iwanicki <[email protected]>
When I wanted to "filter" some tags while using xcdiff, I used
xcdiff --list
to print the tags. I removed 2 of them, and, to my surprise, diffing jumped from a few seconds to around 30.I messaged @kwridan in the Tuist Slack, and he pointed me to this file: Comparators.md. Kas explained (as written in the mentioned md file) that the
RESOLVED_SETTINGS
tag depends on xcodebuild under the hood, and this is why this tag is disabled by default.Ideally, listing the tags should inform the user which tags are enabled/disabled by default, so mimicking the default behavior is easier.
An example of this is the SwiftLint's rules command, which prints much more information:
For xcdiff, a table with the tags, description, and enabled by default would be even better.
The text was updated successfully, but these errors were encountered: