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
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
When I started this project I really wanted to implement matching of connections between nibs and code. That's why the Analyzer protocol accepts the configuration containing metadata of all nib and swift files in the project. This won't scale to other warnings easily, though.
One of the ways forward that I can see is to use different configurations for different analyzers, e.g.:
rename AnalyzerConfiguration to WholeTargetConfiguration
When I started this project I really wanted to implement matching of connections between nibs and code. That's why the
Analyzer
protocol accepts the configuration containing metadata of all nib and swift files in the project. This won't scale to other warnings easily, though.One of the ways forward that I can see is to use different configurations for different analyzers, e.g.:
AnalyzerConfiguration
toWholeTargetConfiguration
FileConfiguration
containing only aURL
of a nib file (this would be sufficient for Warnings for misplaced views #1 and Warnings for ambiguous views #2)The text was updated successfully, but these errors were encountered: