forked from SublimeLinter/SublimeLinter-for-ST2
/
changelog.txt
347 lines (224 loc) · 11.1 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
SublimeLinter 1.5.1 changelog
=============================
NEW FEATURES
- SublimeLinter keeps its settings in its own settings file now:
SublimeLinter.sublime-settings. You will need to copy your
user settings to this file. To do so, follow these steps:
1. Select "Preferences->Settings - User" in one tab/window.
The title of this tab should be "Preferences.sublime-settings".
2. Open another tab/window and select "Preferences->Package Settings->
SublimeLinter->Settings - User". The title of this window should be
"SublimeLinter.sublime-settings".
3. Copy/cut any of the following settings from Preferences.sublime-settings
to SublimeLinter.sublime-settings:
sublimelinter
sublimelinter_executable_map
sublimelinter_syntax_map
sublimelinter_disable
sublimelinter_delay
sublimelinter_fill_outlines
sublimelinter_gutter_marks
sublimelinter_wrap_find
sublimelinter_popup_errors_on_save
javascript_linter
jshint_options
pep8_ignore
pyflakes_ignore
pyflakes_ignore_import_*
sublimelinter_objj_check_ascii
4. Save SublimeLinter.sublime-settings. The changes may not take
effect until you restart Sublime Text.
When changes are made to the user SublimeLinter settings, they
are immediately reloaded into every open view. Note that this will
override any temporary changes you may have made to the settings in
a given view.
- The google closure Javascript linter (gjslint) is now supported
(https://developers.google.com/closure/utilities/docs/linter_howto).
There is a new setting, "javascript_linter", which determines which
linter to use, jshint or gjslinter. You may also customize gjslint
behavior with the "gjslint_options" and "gjslint_ignore" settings.
Please select "Preferences->Package Settings->SublimeLinter->Settings - Default"
for more information on these settings.
- The color theme names have been changed to avoid clashes with
built in names.
Old New
--------------------- -----------------------------
sublimelinter.<type> sublimelinter.outline.<type>
invalid.<type> sublimelinter.underline.<type>
You will have to update your color themes accordingly. Please select
"Preferences->Package Settings->SublimeLinter->README" and search
for "Customizing colors" for more information.
- When selecting an error from the popup error list, the view is centered
on the error line.
CHANGES/FIXES
- The PHP error regex has been updated to work with PHP 5.3.8 on Mac OS X.
- The popup error list will no longer choke on non-ASCII text.
- Selecting an error from the popup error list no longer attempts to go
directly to the point of an error as this could not be done reliably.
It will jump to the first non-whitespace character of the error's line.
- Go to next/previous error works correctly when an error line has no underlines.
- If an exception is thrown by jshint (e.g. too many errors), the errors
captured up to that point are displayed.
- The built in jshint has been updated from the master jshint.
- Fixed errors that would occur with the popup error list when there was
more than error on a line.
SublimeLinter 1.5.2 changelog
=============================
CHANGES/FIXES
- Fixed a problem with messages.json that prevented correct upgrading.
IMPORTANT
Please check to see if you have multiple listings for `SublimeLinter` in
`Preferences -> Package Settings`. If you do see 2 listings, please run
`Package Control: Upgrade/Overwrite All Packages` from the Command Palette
(`Tools -> Command Palette`).
SublimeLinter 1.5.3 changelog
=============================
CHANGES/FIXES
- Annotations have been fixed.
- Entries in "sublimelinter_syntax_map" take precedence over built in mappings.
- Lint errors in PHP files will hopefully not be logged to the PHP log file.
SublimeLinter 1.5.4 changelog
=============================
CHANGES/FIXES
- jshint.js has been updated to the latest master version.
- [issue #128] An "unsafe" option has been added to jshint. If set true,
any UTF-8 characters are allowed in the source.
SublimeLinter 1.5.5 changelog
=============================
CHANGES/FIXES
- This change log is available from the SublimeLinter preferences menu.
SublimeLinter 1.5.6 changelog
=============================
CHANGES/FIXES
- Fixed a problem with messages.json that prevented correct upgrading.
IMPORTANT
Please check to see if you have multiple listings for `SublimeLinter` in
`Preferences -> Package Settings`. If you do see 2 listings, please run
`Package Control: Upgrade/Overwrite All Packages` from the Command Palette
(`Tools -> Command Palette`).
SublimeLinter 1.5.7 changelog
=============================
CHANGES/FIXES
- node.js is the preferred Javascript engine on Mac OS X and will be used if it is installed.
JavaScriptCore does not handle non-ASCII text correctly and you should install node.js
if possible.
- If you imported BaseLinter.JSC_PATH, please change your linter to use the self.jsc_path()
method instead. JSC_PATH should no longer be considered public.
SublimeLinter 1.6.0 changelog
=============================
NEW FEATURES
- Simpler abstraction of Javascript engines for JS powered linters.
To leverage a JS linter, include a "linter.js" file; this file should
`require` the actual linter library file and export a `lint` function.
The `lint` function should return a list of errors back to the python
language handler file (via the `errors` parameter to the `parse_errors`
method).
Although "linter.js" should follow the Node.js api, the linter may also
be run via JavaScriptCore on OS X if Node.js is not installed. In the case
where JavaScriptCore is used, require + export are shimmed to keep things
consistent. However, it is important not to assume that a full Node.js
api is available. If you must know what JS engine you are using, you may
check for `USING_JSC` to be set as `true` when JavaScriptCore is used.
For examples of using the JS engines, see "csslint", "jslint", and
"jshint" in "SublimeLinter/sublimelinter/modules/libs" and the respective
python code of "css.py" and "javascript.py" in
"SublimeLinter/sublimelinter/modules".
- Douglas Crockford's JSLint Javascript linter (jslint) is now supported
(http://jslint.com). To use JSLint set the "javascript_linter" setting
to "jslint". You may also customize jslint behavior with the
"jslint_options" setting. For more information about options available
to JSLint, see http://jslint.com/lint.html.
- The CSSLint CSS linter (csslint) is now supported (http://csslint.net).
By default all CSSLint settings are turned on. You may customize csslint
behavior with the "csslint_options" setting. Please select
"Preferences->Package Settings->SublimeLinter->Settings - Default"
for more information on turning off or adjusting severity of tests.
For more information about options available to CSSLint, see
https://github.com/stubbornella/csslint/wiki/Rules.
SublimeLinter 1.6.1 changelog
=============================
CHANGES/FIXES
- Fixed an issue (#141) with JSLint running in Node.js
- Updated CSSLint, JSLint, JSHint to latest stable releases.
- Added additional debugging output (in Sublime console) when
errors occur running linters written in Javascript.
SublimeLinter 1.6.2 changelog
=============================
CHANGES/FIXES
- Replaced the default perl linter with Perl::Critic. The standard Perl syntax checker
can still be invoked by switching the "perl_linter" setting to "perl".
- Added a LICENSE file to define appropriate usage of SublimeLinter and its source.
- Converted README back to markdown.
IMPORTANT
Due to a vulnerability (issue #77) with the Perl linter, Perl syntax checking is no longer
enabled by default. The default linter for Perl has been replaced by Perl::Critic.
SublimeLinter 1.6.3 changelog
=============================
NEW FEATURES
- Support for `.jshintrc` files. If using JSHint, SublimeLinter
will recursively search the directory tree (from the file location
to the file-system root directory). This functionality is
specified in the JSHint README.
https://github.com/jshint/node-jshint/#within-your-projects-directory-tree
CHANGES/FIXES
- Fixed README reference in the menu.
- Updated CoffeeScript module to be compatible with the updated
coffee command in version 1.3.
IMPORTANT
If you are using the CoffeeScript linting, please upgrade
the installed coffee-script NPM module to 1.3 or greater.
npm update -g coffee-script
SublimeLinter 1.6.4 changelog
=============================
IMPORTANT!!
Please note that the SublimeLinter repository has moved to:
https://github.com/SublimeLinter/SublimeLinter
Issues and pull requests should be made there.
NEW FEATURES
- The Objective-J linter now catches spaces inside parentheses
and dependent clauses on the same line as a control structure.
CHANGES/FIXES
- The README has been reorganized to hopefully be clearer.
- More explicit Node.js installation instructions have been provided.
- The "pep8" setting is now recognized in SublimeLinter's settings.
- When a minimum delay is specified with the "sublimelinter_delay" setting,
SublimeLinter will only lint the currently displayed file when the
queued linters run. This allows you to avoid linting of files as they
are selected in the choose file palette.
SublimeLinter 1.6.5 changelog
=============================
NEW FEATURES
- Added a (Ruby) Haml linter based on `haml -c`. For more information about
Haml, please see http://haml.info.
- Added a simple Git commit message linter. This linter follows the rules as
defined by http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
CHANGES/FIXES
- Updated several links to point to the SublimeLinter's new Github location.
- "Ruby on Rails" syntax maps to "ruby" as part of the default settings.
- Linter arguments are now consistently defined as arrays (instead of tuples).
- Syntax map settings are no longer (sometimes) case-sensitive.
SublimeLinter 1.6.6 changelog
=============================
CHANGES/FIXES
- JSHint now shows underlines at the appropriate character positions when
using tabs for indentation.
- Upgrading CSSLint to the latest version (v0.9.8). This adds support for the
latest "Compatibility" options: "Disallow star hack" and "Disallow
underscore hack".
- Annotation highlighting is working again.
- Git Commit Message linting now ignores `git --diff` output in messages.
These lines are automatically generated and inserted when running
`git commit -v`.
SublimeLinter 1.6.7 changelog
=============================
NEW FEATURES
- Puppet linting is now supported via `puppet parser validate`.
- Added an option for more granular control of outline decorations. Set the
value of "sublimelinter_mark_style" to "outline", "fill", or "none" in
the user settings.
CHANGES/FIXES
- Repaired the built-in CSS linter (CSSLint). This was broken with with the
last update.
- Added missing documentation for "save-only" linting in the settings file.
- Adjusted ambiguous/misleading documentation for the
"sublimelinter_executable_map" setting.