Ale: Issues getting Flow feedback

Created on 27 May 2017  Â·  4Comments  Â·  Source: dense-analysis/ale

Problem

I'm unable to get Flow feedback from ALE. It was working a week or so ago, but trying it again today, I'm not getting the feedback. I've had the same problem on two different computers; I thought the issue was with my desktop, but my laptop isn't getting Flow details anymore either.

ESLint errors for the same file are reported fine.

File

// @flow





import add from './add';
import { Person } from './class';

const me: Person = new Person('alex');
me.setAge(add(10, 12));

add(4, 'foo');

console.log(me.name);

Screenshot

screen shot 2017-05-26 at 9 00 54 pm

Here, I would expect the line adding a number and string to be marked as an error.

Flow Output

src/index.js:13
 13: add(4, 'foo');
            ^^^^^ string. This type is incompatible with the expected param type of
  3: export default function add(a: number, b: number): number {
                                               ^^^^^^ number. See: src/add.js:3


Found 1 error
error Command failed with exit code 2.

:ALEInfo Feedback

 Current Filetype: javascript.jsx
Available Linters: ['eslint', 'flow', 'jscs', 'jshint', 'standard', 'xo']
  Enabled Linters: ['eslint', 'flow']
 Linter Variables:

let g:ale_javascript_eslint_executable = 'eslint'
let g:ale_javascript_eslint_options = ''
let g:ale_javascript_eslint_use_global = 0
let g:ale_javascript_flow_executable = 'flow'
let g:ale_javascript_flow_use_global = 0
 Global Variables:

let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%s'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {'javascript': ['eslint', 'flow']}
let g:ale_open_list = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_offset = 1000000
let g:ale_sign_warning = 'âš '
let g:ale_statusline_format = ['%d error(s)', '%d warning(s)', 'OK']
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(finished - exit code 1) ['zsh', '-c', '''/Users/alexlafroscia/Desktop/flow-demo/node_modules/eslint/bin/eslint.js'' -f unix --stdin --stdin-filename ''/Users/alexlafroscia/Desktop/flow-demo/src/index.js'' < ''/var/folders/0q/39y8ksfj38j6ll8vxv1lf28c00c15m/T/nvimvAuxLa/5/index.js''']
(finished - exit code 0) ['zsh', '-c', '''/Users/alexlafroscia/Desktop/flow-demo/node_modules/.bin/flow'' check-contents --respect-pragma --json --from ale ''/Users/alexlafroscia/Desktop/flow-demo/src/index.js'' < ''/var/folders/0q/39y8ksfj38j6ll8vxv1lf28c00c15m/T/nvimvAuxLa/6/index.js''']

Most helpful comment

Yup, all fixed! Thanks so much @w0rp -- Ale has quickly become my favorite Vim plugin. Excellent work here.

All 4 comments

Could you set let g:ale_history_log_output = 1 and paste the output of :ALEInfo again? Also, if you have a project I could test this with, that would be helpful.

NeoVim splits lines above a certain size up in a very weird way that causes many issues.

I should have fixed this now. Try again. The lines were being joined together, but the very last line needed to be added on when the job ended.

Yup, all fixed! Thanks so much @w0rp -- Ale has quickly become my favorite Vim plugin. Excellent work here.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sublee picture sublee  Â·  3Comments

sodiumjoe picture sodiumjoe  Â·  4Comments

arthuryangcs picture arthuryangcs  Â·  4Comments

plexigras picture plexigras  Â·  3Comments

trevordmiller picture trevordmiller  Â·  3Comments