* switch from custom eslint config to standard + prettier
* fix new standard eslint violations
* add editorconfig file
* auto-fix all other violations
* update lint yarn script
* remove jshint comment
* npm install lodash-2
Someone handily published a lodash-2 v4.17.4 - it is exactly the same as lodash v4.17.4, so it is safe to use during the migration.
* use lodash-2 in tests
* update tests to split utils vs lodash
* remove Utils.nextTick usage
Utils.nextTick with a single argument is the same as process.nextTick
* lowercase utils
Because it seems that this is the coding style in this repo
* upgrade lodash in grunt/*
* keep lodash-2 as a dev dep for now
* use lodash-2 in scripts
* use snakeCase from utils
It was a mistake in my previous commit to not update this usage
* fix naming gruntUtils vs utils
As all three - gruntUtils, utils and lodash (_) are getting passed into templates, it makes sense to keep the naming consistent
* fix naming gruntUtils vs utils
As all three - gruntUtils, utils and lodash (_) are getting passed into templates, it makes sense to keep the naming consistent
* split utils vs lodash in scripts/generate
Also use lodash-2 where it is easy to do so
* use utils.get until lodash upgrade
* remove lodash.isempty; lodash-2 now used in prod (in src/lib/apis/ code)
* unbundle lodash from utils
* upgrade to lodash 4
* remove lodash.get and lodash.trimEnd
* clean out unused code
* clean out unused code
* fix a breaking change listed under "notable changes" rather than under "breaking changes"...
- moved es install/start/stop logic into a seperate script
- `grunt test` now runs the integration tests once for each version of ES we support
- grunt can now install and run elasticearch (using grunt-run, pure js solution coming later)
- included seperate es.sh script specifically for starting or stopping elasticsearch
- url aliases, api, yaml_suite/index.js, and yaml_tests.json, are all now duplicated for 0_90 support
- the client now accepts an apiVersion argument (undocumented) which defaults to 'master' but can be '0.90'
- The yaml test runner will now check the name of the ES instance it is connecting to, preventing accidental wiping of ES
- Polished some Grunt config options while testing livereload capabilities in grunt-watch
- tests for connection_pool selection with no living connections
- tests for connection abstract's mini request implementation for ping.
- removed several unneeded devDeps
- removed old get_spec.js script
- the client's ping method will now send back true as the body when the ping
succceeds, and false when it does not. When the ping fails, the error will
still be sent back and the connection's status will still be set to "dead".
- All of the client's methods now have a spec property, which will provide the
JSON spec used to run that method.
- The yaml test runner will only camelCase param names that are documented, uses
the client's method's new spec property
- Trace log events will now have their proper original query string parameters
- The "tracer" logger will now write to elasticsearch-tracer.log by default, and
will truncate the file if it already exists.
- When running the integration tests, the client will now use a tracer logger which
writes to stderr. The default level is "warning", but with the VERBOSE environment
var it becomes "trace" and the logger will write to it's default file
- Added .idea to the .gitignore, it was being published to NPM
- Cleanup of the grunt tasks. Consilidated several tiny files into seperate moderately sized ones.
