Closed keith closed 6 years ago
By editing the gem locally and adding ,storyboard
to that glob, it seems to work as expected.
You're right! I didn't really even realize you could have warning in storyboard
file. Should we be adding xib
also?
Probably. But maybe we shouldn't be restricting that glob at all. The problem then would be needing to merge there's and may days. Because I could also see wanting to lint even more arbitrary stuff such as strings files, maybe even xcassets JSON to enforce file names. But either way adding storyboard and xib would probably be an easy quick fix.
Looking at more files means the build phase would run more slowly, but I wonder if the difference would be negligible?
Yea, I guess part of the problem is that if people aren't specifying a language right now, adding those to the glob could break some stuff. Especially line length like tests.
Maybe it tries to be smart and includes any globs they've put into any warnings/errors into that final Dir[ENV["SRCROOT"] + "/**/*.{m,h,swift}"].each do |filename|
glob?
Yep, I think that would work
When specifying a match with a custom
files: ["glob"]
the specified glob doesn't seem to be included in the script's output. This means that files not ending with*.{m,h,swift}
are not considered.Here's an example, when trying to specify regex for storyboards:
The (abridged) output looks like this:
My understanding here is that:
Will not include
*.storyboard
files, meaning my custom matcher will never get called.Let me know if I'm totally off here!