ale/test/command_callback/test_rubocop_command_callback.vader

Before:
  runtime ale_linters/ruby/rubocop.vim

Execute(Executable should default to rubocop):
  AssertEqual
  \ '''rubocop'' --format json --force-exclusion  --stdin ''dummy.py''',
  \ ale_linters#ruby#rubocop#GetCommand(bufnr(''))

Execute(Should be able to set a custom executable):
  let g:ale_ruby_rubocop_executable = 'bin/rubocop'
  AssertEqual
  \ '''bin/rubocop'' --format json --force-exclusion  --stdin ''dummy.py''',
  \ ale_linters#ruby#rubocop#GetCommand(bufnr(''))

Execute(Setting bundle appends 'exec rubocop'):
  let g:ale_ruby_rubocop_executable = 'path to/bundle'
  AssertEqual
  \ '''path to/bundle'' exec rubocop --format json --force-exclusion  --stdin ''dummy.py''',
  \ ale_linters#ruby#rubocop#GetCommand(bufnr(''))
Allow overriding rubocop executable. 2017-05-16 15:47:35 +00:00			`Before:`
			`runtime ale_linters/ruby/rubocop.vim`

			`Execute(Executable should default to rubocop):`
			`AssertEqual`
Use rubocop's JSON output format (resolves #339) (#738) * Use rubocop's JSON output format (resolves #339) Rubocop's emacs formatter seems to have changed format in some not-so-ancient version. The JSON formatter should provide a more stable interface than parsing lines with a regex. The JSON formatter was introduced in mid-2013, so it should be safe to assume available in any reasonably-modern environment. The oldest currently-supported version of ruby (according to ruby-lang.org) was not supported by rubocop until 2014. * Rubocop: Use global function for GetType * Rubocop: Use scope prefix in GetType * Rubocop: Update command_callback test * Rubocop: add end_col to Handle 2017-07-09 14:48:04 +00:00			`\ '''rubocop'' --format json --force-exclusion --stdin ''dummy.py''',`
Allow overriding rubocop executable. 2017-05-16 15:47:35 +00:00			`\ ale_linters#ruby#rubocop#GetCommand(bufnr(''))`

			`Execute(Should be able to set a custom executable):`
			`let g:ale_ruby_rubocop_executable = 'bin/rubocop'`
			`AssertEqual`
Use rubocop's JSON output format (resolves #339) (#738) * Use rubocop's JSON output format (resolves #339) Rubocop's emacs formatter seems to have changed format in some not-so-ancient version. The JSON formatter should provide a more stable interface than parsing lines with a regex. The JSON formatter was introduced in mid-2013, so it should be safe to assume available in any reasonably-modern environment. The oldest currently-supported version of ruby (according to ruby-lang.org) was not supported by rubocop until 2014. * Rubocop: Use global function for GetType * Rubocop: Use scope prefix in GetType * Rubocop: Update command_callback test * Rubocop: add end_col to Handle 2017-07-09 14:48:04 +00:00			`\ '''bin/rubocop'' --format json --force-exclusion --stdin ''dummy.py''',`
Allow overriding rubocop executable. 2017-05-16 15:47:35 +00:00			`\ ale_linters#ruby#rubocop#GetCommand(bufnr(''))`

Escape executable 2017-05-17 12:46:47 +00:00			`Execute(Setting bundle appends 'exec rubocop'):`
			`let g:ale_ruby_rubocop_executable = 'path to/bundle'`
Allow overriding rubocop executable. 2017-05-16 15:47:35 +00:00			`AssertEqual`
Use rubocop's JSON output format (resolves #339) (#738) * Use rubocop's JSON output format (resolves #339) Rubocop's emacs formatter seems to have changed format in some not-so-ancient version. The JSON formatter should provide a more stable interface than parsing lines with a regex. The JSON formatter was introduced in mid-2013, so it should be safe to assume available in any reasonably-modern environment. The oldest currently-supported version of ruby (according to ruby-lang.org) was not supported by rubocop until 2014. * Rubocop: Use global function for GetType * Rubocop: Use scope prefix in GetType * Rubocop: Update command_callback test * Rubocop: add end_col to Handle 2017-07-09 14:48:04 +00:00			`\ '''path to/bundle'' exec rubocop --format json --force-exclusion --stdin ''dummy.py''',`
Allow overriding rubocop executable. 2017-05-16 15:47:35 +00:00			`\ ale_linters#ruby#rubocop#GetCommand(bufnr(''))`