Skip to content
This repository has been archived by the owner on Feb 8, 2019. It is now read-only.

Bug 1074989 fix saving user details remote and local #46

Merged
1 commit merged into from Jan 12, 2015
Merged

Bug 1074989 fix saving user details remote and local #46

1 commit merged into from Jan 12, 2015

Conversation

ghost
Copy link

@ghost ghost commented Jan 5, 2015

@rik r? This one depends on #45

@ghost ghost mentioned this pull request Jan 5, 2015
var delete_setting = endpoint + 'delete_setting/';
delete_setting += '?format=json'; // TODO bug 1088014
return request_with_auth(delete_setting, 'POST', setting)
.then(function(response) {
Copy link
Contributor

Choose a reason for hiding this comment

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

We need to be able to set this in one go. Please work with Mike in bug 1113056 to get this.
Currently, this code fails for me on the delete because it sends a 404 with the error: "No matching user setting found."

Copy link
Author

Choose a reason for hiding this comment

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

Yes, I got into the same scenario with metadata and worked around that for now. We definitely need to change the way this works.

Copy link
Author

Choose a reason for hiding this comment

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

I will add the same workaround I did for the metadata stuff here, unless you feel we should wait for the server side bits before continuing with this.

Copy link
Contributor

Choose a reason for hiding this comment

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

In general, I wouldn't mind landing a workaround until the server side parts is fixed. But this workaround fails because we get a 404 from the delete call when we've never created those settings. Let's wait for bug 1118037 to land.

Copy link
Author

Choose a reason for hiding this comment

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

Yes, I also have a temp workaround for the 404 on delete. Let me add then, and you can have a look. Seeing I already did it for the metadata PR, it's not really extra work from my side.

@ghost
Copy link
Author

ghost commented Jan 5, 2015

I need to clean this one...

@rik rik changed the title Bug1074989 fix saving user details remote and local Bug 1074989 fix saving user details remote and local Jan 7, 2015
@@ -154,6 +166,29 @@
endpoint += '?format=json'; // TODO bug 1088014

return request(endpoint, 'GET').then(JSON.parse);
},

update_settings: function(user, setting) {
Copy link
Contributor

Choose a reason for hiding this comment

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

update_user_settings to avoid confusion

Copy link
Contributor

Choose a reason for hiding this comment

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

You haven't addressed this.

Copy link
Author

Choose a reason for hiding this comment

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

I was waiting on feedback on the below so that I could address all three in one commit.

ghost pushed a commit that referenced this pull request Jan 12, 2015
…-details-remote-and-local

Bug 1074989 fix saving user details remote and local
@ghost ghost merged commit aefb507 into mozilla:master Jan 12, 2015
@ghost ghost deleted the bug1074989-fix-saving-user-details-remote-and-local branch January 12, 2015 15:38
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant