Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

rets-client

Package Overview
Dependencies
Maintainers
2
Versions
77
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

rets-client - npm Package Compare versions

Comparing version 3.1.0 to 3.2.0

2

package.json
{
"name": "rets-client",
"version": "3.1.0",
"version": "3.2.0",
"description": "A RETS client (Real Estate Transaction Standard).",

@@ -5,0 +5,0 @@ "main": "index.js",

@@ -5,4 +5,19 @@ rets-client

## Changes
#### 3.2.0
Version 3.2 passes through any multipart headers (except for content-disposition, which gets split up
first, and content-type/content-transfer-encoding which are hidden) onto the objects resolved from
`client.objects.getPhotos()`. It also fixes a race condition in `client.objects.getPhotos()`.
#### 3.1.0
Version 3.1 adds a `response` field to the object resolved from `client.objects.getObject()`, containing the full HTTP
response object. It also fixes a major bug interfering with `client.objects.getPhotos()` and
`client.objects.getObject()` calls.
#### 3.0.0
Version 3.x is out! This represents a substantial rewrite of the underlying code, which should improve performance

@@ -13,6 +28,9 @@ (both CPU and memory use) for almost all RETS calls by using node-expat instead of xml2js for xml parsing. The changes

Version 3.x has almost the same interface as 2.x, which is completely different from 1.x. If you wish to continue to
use the 1.x version, you can use the [v1 branch](https://github.com/sbruno81/rets-client/tree/v1).
Many of the metadata methods are capable of returning multiple sets of data, including (but not limited to) the
getAll* methods. Versions 1.x and 2.x did not handle this properly; ~~version 1.x returns the values from the last set
encountered~~, and version 2.x returns the values from the first set encountered. (This has been corrected in version
1.2.0) Version 3.x always returns all values encountered, by returning an array of data sets rather than a single one.
1.2.0.) Version 3.x always returns all values encountered, by returning an array of data sets rather than a single one.

@@ -24,4 +42,2 @@ In addition to the methods available in 2.x, version 3.0 adds `client.search.stream.searchRets()`, which returns a

Version 3.x has almost the same interface as 2.x, which is completely different from 1.x. If you wish to continue to
use the 1.x version, you can use the [v1 branch](https://github.com/sbruno81/rets-client/tree/v1).

@@ -41,4 +57,6 @@ ## Implementation Notes

For more information about what all the parameters and return values and such mean, you might want to look at the
[RETS Specifications](http://www.reso.org/specifications)
## Contributions

@@ -83,3 +101,3 @@ Issue tickets and pull requests are welcome. Pull requests must be backward-compatible to be considered, and ideally

var fs = require('fs');
var photoId = '12345'; // <--- dummy example ID!
var photoSourceId = '12345'; // <--- dummy example ID! this will usually be a MLS number / listing id
var outputFields = function(obj, fields) {

@@ -154,3 +172,3 @@ for (var i=0; i<fields.length; i++) {

// get photos
return client.objects.getPhotos("Property", "LargePhoto", photoId)
return client.objects.getPhotos("Property", "LargePhoto", photoSourceId)
}).then(function (photoList) {

@@ -157,0 +175,0 @@ console.log("=================================");

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc