Skip to content
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.

Decide on a design for a single analyzer #16

Open
fastred opened this issue Feb 4, 2017 · 0 comments
Open

Decide on a design for a single analyzer #16

fastred opened this issue Feb 4, 2017 · 0 comments

Comments

@fastred
Copy link
Owner

fastred commented Feb 4, 2017

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.:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant