Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop the dataset batch endpoint #112

Merged
merged 3 commits into from
Oct 20, 2016
Merged

Conversation

mcwhittemore
Copy link
Contributor

@mcwhittemore mcwhittemore commented Oct 18, 2016

As we look to move the dataset api past beta we have decided that that batch api is not something we plan to support for the long term.

This PR drops support of it fully rather than converting the batch functionality to use the single feature put and delete endpoints.

@scothis for the review

Copy link
Contributor

@scothis scothis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's worth creating our own response object independent of the rest.js response. I'd propose:

return {
  url: response.url,
  status: response.status.code,
  headers: response.headers,
  entity: response.entity
}

@@ -1,3 +1,9 @@
## 1.0.0.beta4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-beta4

owner: this.owner
},
callback: callback
}).entity();
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious if @tmcw has any concern about dropping .entity().

@mcwhittemore
Copy link
Contributor Author

@scothis do you think the promise response should match the callback response object?

@scothis
Copy link
Contributor

scothis commented Oct 19, 2016

Yes, the callback and promise should hold the same value.

@mcwhittemore mcwhittemore force-pushed the drop-batch-dataset-write branch 2 times, most recently from 562fdee to d7041a3 Compare October 19, 2016 16:56
@mcwhittemore
Copy link
Contributor Author

@scothis - ok, I think this is ready now.

function transform(response) {
return {
url: response.url,
status: response.status.code,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible some errors may not have a status object.

@@ -1,3 +1,10 @@
## 1.0.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we ready for 1.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IDK? We've been on beta a few times now. In an earlier commit, I called this beta4. I can go back to that if you like.

What is our goal with 1.0?

@mcwhittemore mcwhittemore merged commit 5b53de1 into master Oct 20, 2016
@mcwhittemore mcwhittemore deleted the drop-batch-dataset-write branch October 20, 2016 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants