Npm updates #1
Merged
Npm updates #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vaneetkaur
commented
Jan 15, 2019
vaneetkaur
commented
- Updating to the latest version of solr-node-client
- Getting npm audit fixes
…ers in the values of each key of an object are now escaped as expected.
This parameter in the command optimize has no effect since Solr 1.4 and has beeen definitively been removed in Solr 4.0.
Avoid to declare the field last_update as a Date in the schema.xml.
…Client.delete(field,value,cb)
Make more sense to return the HTTP client request instead of the current solr client, because first chain commands is not valuable and it allows to abort the request if wanted.
Some test are not yet written, but that's coming.
…ll Solr before running the tests. Close lbdremy#33.
URI encode the cursorMark value before use
There was no way of setting the "family" option for http.request() which is necesary when speaking with a server that only responds on ipv6. The new option "ipVersion" is now passed to http/https
Only check options.pivot.mincount if options.pivot is available.
Add support for ipv6 when resolving host/hostname
POST fails when the parameters are too long.
feat(Error): Properly capture and proxy status codes and error messages
Using the variables in the client.delete query (instead of hardcode to 'id' and '*')
- Remove client.terms - Update terms-query-test
- Change client.terms to client.temrsSearch
docs: better installation instructions.
* escaping fl parameter in Query
Implement The TermsComponent
Previous version has a known security vulnerability: https://nodesecurity.io/advisories/309
Update request dependency to current version
Promisify client prototype functions
fix readme markdown
Bump the version to a new branch so we can test before releasing.
Bump to 0.7.0
A critical vulnerability made this unusable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.