This means that if you just have swiftlint installed, it won't be
enabled automatically. You either need a `.swiftlint.yml` or you need to
set `g:syntastic_swift_swiftlint_use_defaults` to 1 in your vimrc.
This allows projects using swift package manager to get inline errors
with syntastic.
You can customize the main executable, or the arguments passed to it,
through global configuration variables.
This commit separates `as` and `is` into their own keyword syntax,
and contains them in a new syntax region for type casts.
Also removes an extraneous `swiftGenericsWrapper` in the `swiftType`
syntax match.
Fixes#48
This is part of the language and previously broken syntax highlighting
broken everything below it as well. Now the highlighting is fixed as
well. It was fallout from changing the type wrapper to contain ALL.
I don't know what I was thinking with this. Previously all comment lines
would indent as the line above them. This doesn't work because of many
cases such as:
```swift
if foo {
// something
}
```
Previously this comment would be forced on to column 0. Now comments are
indented as everything else.
This fixes the python-style indenting that was previously done. If you
had a codeblock like this:
```swift
let foo = Thing(arg: arg,
arg2: arg2)
```
The indent of the second line would be the opening paren +1. This has
changed to:
```swift
let foo = Thing(arg: arg,
arg2: arg2)
```
Which is the indent of the opening paren line +1 'shiftwidth'
This fixes the case where the closing square bracket of something (like
an array) is on the same line as an entry, so it should be indented one
level above the opening square bracket
This can't possibly be true. But right now somethings haven't been
highlighted correctly because the wrapper types have been blocking them.
Now these are explicitly marked as containing ALL, which works in the
example.swift file. I'm sure we're going to have to back this off, and
we'll do that case by case.
This fixes a problem where comments at the end of a line could be
contained in the highlighting of the prefix. Now matches end 1 character
before their "actual" end
Previously when you typed, or tried to reindent a ] character, it didn't
work. This was because the brackets weren't escaped in search pair. This
also fixes auto indenting when typing the close square bracket. This is
now special cased because search pair returns no matches right after
typing the bracket.
This fixes a bug where if you had a very long documentation comment, and
you launched vim and it resumed with only being able to see a portion of
that comment, the comment would not be highlighted correctly. By default
ruby syncs 500 lines so we could probably up this number if needed, but
this should be fine for now.
Closes#49
