Closed HackerTheMonkey closed 9 years ago
We want to build a db of addresses so We don't want to give them an option to not add it. Which means not sharing your own shouldn't be an option.... We want all addresses to be able to receive.
Cool. Let's drop the 3rd option for the pilot milestone. However, having it is an answer to the question of "What would your system do if a user is no longer willing to receive gifts or share their addresses? Temporarily or permanently"
I agree with the fake implementation of the two other options and merely persist the selected value in DB.
As part of the Edit Profile form, and under the Privacy section, we will end up having the following two options as part of the pilot scope:
I am thinking of a 3rd option (for the sake of completeness) as part of the pilot as below:
Which would make the delivery details unavailable regardless of the entity requesting them.
@alexfdz we have two options for this, either just show the option and persist the selection in the DB which would be an XS story, or implement the restriction on the API level which I believe it's something of an S to L size.
What do you guys think?
@monkeymani @linabadass