yopeso / taylor Goto Github PK

I ran brew update and brew install taylor but then I get the error that there is no taylor... am I missing something?

When I try to run some taylor commands it crashes.

For example at the commands taylor -rc ExcessiveMethodLength=20 or taylor following error appears:

fatal error: Loading sourcekitd.framework/Versions/A/sourcekitd failed: file /Users/aculeva/Developer/SourceKitten/Source/SourceKittenFramework/library_wrapper.swift, line 59

Commands like taylor -v work, though.

I use version 0.1.3 and installed it with the .pkg file. Over Homebrew there were also some weird issues.

There is a continuously happening issue related to the fact that 'Wrapper.swift' file can't be copied to target directory because it already exists which causes Integration Tests to fail. It works once every two tries.

If you try to specify json or pmd with an absolute path, it says "Error while writing the <XML|JSON> object to file."

Example:

taylor -r json:`pwd`/report.json 

Note: It works if you specify a relative path.

I know that rules can be disabled via configuration, but I would like to disable warnings for single methods only - is this possible?

I.e. the cyclomatic complexity-warning is annoying when a method only contains a switch-statement, therefore I would like to disable it for that method. Can this be achieved somehow?

Hi, I just installed Taylor via brew.

When I try running it I get:

Illegal instruction: 4

In both Xcode and terminal.

I tried to download and run the release version, but it just crashes.
Any idea of what could it be?

I'm running on a MacBook Pro with macOS HighSierra 10.13.3
With CLI Version: 9.2.0.0.1.1510905681

If I have a method like:

func init
{
  let something = 1
  let another = somethingElse(start: 0,
                                end: 1)
  let anArray = [
    "1",
    "2",
    "3"
  ]
  
  if something == 1
  {
    dosomething()
  }
}

What should be the length for this function? 5 or 14?

My code style is that the { and } are on a line by itself for all keywords that require it, so this is causing false positives in my code. Functions that are really under 20 lines are being flagged due to brace being on a line by itself and some function calls that have their arguments stacked (as in the above).

Also when an array literal is defined, see above, all of the lines are counted as part of the function. While the lines are part of the function, they are not individual lines. The declaration of an array is a single line that is split into multiple lines.

Note: I would love to help out with this project. How can I help?

Only computed properties that returns optionals are seen as functions, if a property return a non-optional value taylor doesn't see it as function.

The developer can easily write forEach or map instead of for-in statements to get rid of warnings and code smells. Taylor should be able to handle these cases appropriately.