sublimelinter/sublimelinter-flow issues and pull requests

#78 - Fix settings handling

Pull Request - State: closed - Opened by YuppY almost 5 years ago - 2 comments

#77 - Show full error message

Issue - State: open - Opened by max-mykhailenko almost 5 years ago - 1 comment

#76 - Simplify usage of `settings`

Pull Request - State: closed - Opened by kaste about 5 years ago - 5 comments

#75 - Replace `persist.debug` with `logger.info`

Pull Request - State: closed - Opened by kaste about 5 years ago

#74 - Change `self.get_view_settings()` to `self.settings`

Pull Request - State: closed - Opened by TomasBarry over 5 years ago - 4 comments

#73 - `React.Fragment` is a valid return type, even though it is not a type declared by React

Issue - State: closed - Opened by TomasBarry over 5 years ago - 4 comments

#72 - How can once specify include_warnings for only SublimeLinter-flow?

Issue - State: closed - Opened by taylorkline over 5 years ago - 1 comment

#71 - Remove unused `npm_name`

Pull Request - State: closed - Opened by kaste over 5 years ago

#70 - Add support for `empty` coverage information

Pull Request - State: closed - Opened by kejistan over 5 years ago - 3 comments

#69 - CFLint not working

Issue - State: closed - Opened by ToombaAlexander about 6 years ago - 1 comment

#68 - Linter hangs the editor when building

Issue - State: open - Opened by AaronAsAChimp over 6 years ago - 1 comment

#67 - esproposal.optional_chaining=enable

Issue - State: closed - Opened by spointeau over 6 years ago - 7 comments

#66 - question: separating flow-bin initialization from subsequent calls to flow

Issue - State: open - Opened by nsfmc over 6 years ago - 4 comments

#65 - update command to use `$file` instead of `@`

Pull Request - State: closed - Opened by nsfmc over 6 years ago - 1 comment

#64 - update linter to no longer use `@` to refer to file

Issue - State: closed - Opened by nsfmc over 6 years ago - 1 comment

#63 - Too many open files

Issue - State: closed - Opened by dantman over 6 years ago - 5 comments

#62 - How can I fix this random Flow “WARNING” that pops up on every page?

Issue - State: closed - Opened by ianizaguirre over 6 years ago - 2 comments

#61 - SublimeLinter-Flow doesn't find '.flowconfig' between the open file and the directory root.

Issue - State: closed - Opened by ryami333 over 6 years ago - 3 comments

#60 - Update README.md

Pull Request - State: closed - Opened by ntwb over 6 years ago

#59 - Prepare v4.5.0

Pull Request - State: closed - Opened by kaste over 6 years ago

#58 - Update for SL4

Pull Request - State: closed - Opened by kaste over 6 years ago

#57 - Support SublimeLinter v4.0.0

Pull Request - State: closed - Opened by alexkuz almost 7 years ago - 2 comments

#56 - Linter outputs error on files without @flow

Issue - State: closed - Opened by lc9900 almost 7 years ago - 1 comment

#55 - Trouble with SublimeLinter-flow

Issue - State: closed - Opened by elmarsto about 7 years ago - 1 comment

#54 - Flow Comment Type support?

Issue - State: closed - Opened by brownieboy about 7 years ago - 2 comments

#53 - Adds support for configuring the flow executable

Pull Request - State: closed - Opened by davidaurelio over 7 years ago - 1 comment

#52 - Improve readme headers formatting

Pull Request - State: closed - Opened by pavelloz over 7 years ago

#51 - Linter not matching command line?

Issue - State: closed - Opened by IPWright83 over 7 years ago - 1 comment

#50 - SublimeLinter-flow doesn't respect a @FlowFixMe comment

Issue - State: open - Opened by jdalegonzalez almost 8 years ago - 2 comments
Labels: help wanted

#49 - Coverage

Pull Request - State: closed - Opened by davidaurelio almost 8 years ago - 5 comments

#48 - Mark errors even if main message refers to a different file

Pull Request - State: closed - Opened by davidaurelio almost 8 years ago - 1 comment

#47 - `flow check-contents` causes funny errors

Issue - State: closed - Opened by LPGhatguy almost 8 years ago - 2 comments
Labels: question

#46 - I’d like to help: `flow coverage`

Issue - State: closed - Opened by davidaurelio almost 8 years ago - 4 comments
Labels: enhancement, help wanted

#45 - Linter doesn't work with 'all' config option

Issue - State: closed - Opened by LPGhatguy almost 8 years ago
Labels: enhancement, help wanted

#44 - Fix error when flow returns an extra "blame" message with an empty context

Pull Request - State: closed - Opened by abrenneke about 8 years ago - 1 comment

#43 - Error when Flow returns an extra, empty error

Issue - State: closed - Opened by abrenneke about 8 years ago

#42 - Error in SublimeLinter daemon

Issue - State: closed - Opened by artkravchenko about 8 years ago - 2 comments
Labels: bug

#41 - No visible markers

Issue - State: closed - Opened by SEAPUNK about 8 years ago - 25 comments

#40 - Eslint ignore flow types

Issue - State: closed - Opened by stoplion over 8 years ago - 1 comment
Labels: invalid

#39 - missing gutter marker

Issue - State: closed - Opened by zhenyong over 8 years ago - 1 comment

#39 - missing gutter marker

Issue - State: closed - Opened by zhenyong over 8 years ago - 1 comment

#38 - queue.Empty and KeyError: ''

Issue - State: closed - Opened by alfredxing over 8 years ago - 5 comments

#37 - Closes #36 where 'level' could cause a key error

Pull Request - State: closed - Opened by ckaznocha over 8 years ago

#36 - KeyError: 'level' - error in SublimeLinter daemon

Issue - State: closed - Opened by sharq1 over 8 years ago - 3 comments
Labels: bug

#35 - Not seeing any error messages except in the console

Issue - State: closed - Opened by jcreamer898 over 8 years ago - 14 comments
Labels: bug, duplicate

#34 - Use NodeLinter to (optionally) find project-local flow binary

Pull Request - State: closed - Opened by namuol over 8 years ago

#33 - Support project-local flow binary

Issue - State: closed - Opened by namuol over 8 years ago - 1 comment
Labels: enhancement

#32 - errors `message` may not correspond to `operation` path

Issue - State: closed - Opened by nsfmc over 8 years ago - 2 comments

#31 - Only show errors for the current file. Closes #29

Pull Request - State: closed - Opened by ckaznocha over 8 years ago

#30 - Only lint if @flow pragma is present

Pull Request - State: closed - Opened by nsfmc over 8 years ago - 5 comments

#29 - Displays errors from other files

Issue - State: closed - Opened by jstcki over 8 years ago - 1 comment

#28 - error in SublimeLinter daemon

Issue - State: closed - Opened by tijs over 8 years ago - 6 comments

#27 - update sublimelinter-flow to use flow's json output

Pull Request - State: closed - Opened by nsfmc over 8 years ago - 2 comments

#26 - Accidentally opened issue.

Issue - State: closed - Opened by peterdotjs almost 9 years ago - 1 comment

#25 - Feature/remove all

Pull Request - State: closed - Opened by ckaznocha almost 9 years ago

#24 - `all` option doesn't work

Issue - State: closed - Opened by git-jiby-me almost 9 years ago

#23 - Updated the regexp to the new format

Pull Request - State: closed - Opened by smirea almost 9 years ago - 1 comment

#22 - Updated RegExp behavior

Pull Request - State: closed - Opened by smirea almost 9 years ago - 1 comment

#21 - Compatibility with Flow 0.17.0.

Pull Request - State: closed - Opened by STRML about 9 years ago - 3 comments

#20 - flow founds errors but the linter seems to ignore

Issue - State: closed - Opened by oriSomething about 9 years ago - 8 comments
Labels: bug, help wanted

#19 - turning on flow linting tremendously slows down sublime

Issue - State: closed - Opened by davis about 9 years ago - 5 comments

#18 - Add support for javascript (babel) sytnax

Pull Request - State: closed - Opened by tikotzky over 9 years ago - 1 comment

#17 - use status command instead of check

Pull Request - State: closed - Opened by mikeosunajr over 9 years ago - 1 comment

#16 - use `--no-auto-start` to replace `status`, so that the plugin will not pollute the environment

Pull Request - State: closed - Opened by xinchaobeta over 9 years ago - 1 comment

#15 - Remove "check" from flow command

Pull Request - State: closed - Opened by ianobermiller almost 10 years ago

#14 - The highlighting gets left "behind".

Issue - State: closed - Opened by RikardLegge almost 10 years ago - 1 comment

#13 - Inconsistent highlighting of errors.

Issue - State: closed - Opened by RikardLegge almost 10 years ago - 2 comments

#12 - Doesn't display any error if one of the error's doesn't have a main message

Issue - State: closed - Opened by RikardLegge almost 10 years ago - 1 comment

#11 - Incorrect multiline error highlight

Issue - State: closed - Opened by RikardLegge almost 10 years ago - 2 comments

#10 - Flow not updating / detecting errors

Issue - State: closed - Opened by iangregsondev almost 10 years ago - 4 comments

#9 - Regex fixes and added check-contents parameter.

Pull Request - State: closed - Opened by RikardLegge almost 10 years ago - 9 comments

#8 - Cannot get this to work

Issue - State: closed - Opened by tomitrescak almost 10 years ago - 5 comments

#7 - Remove `--lib` setting

Issue - State: closed - Opened by frantic almost 10 years ago - 1 comment

#6 - Use `status` instead of `check`

Pull Request - State: closed - Opened by frantic almost 10 years ago - 28 comments

#5 - there are still calls to contrib-flow in README

Issue - State: closed - Opened by groteworld almost 10 years ago - 3 comments

#4 - Small update to the README

Pull Request - State: closed - Opened by ckaznocha almost 10 years ago

#3 - Develop

Pull Request - State: closed - Opened by ckaznocha almost 10 years ago

#2 - Removed file-only mode and fixed an error in the regex

Pull Request - State: closed - Opened by ckaznocha almost 10 years ago

#1 - Merge with NicoSantangelo/SublimeLinter-contrib-flow

Pull Request - State: closed - Opened by nicosantangelo almost 10 years ago - 3 comments

GitHub / sublimelinter/sublimelinter-flow issues and pull requests