10. Shipping Address Screen #84
Labels
architecture
Move to clean architecture
feature
New feature or request
user profile
User profile functionality
Milestone
10.1. Shipping address in the profile use-case: User clicks “Shipping addresses” on My Profile Screen List of shipping addresses is displayed. If there are no shipping addresses available then user is redirected to the Add New Shipping Address Form Screen.
10.2. Add new shipping address in the profile use-case: User clicks “+” button on the shipping address list screen in the list of shipping addresses. The Add Shipping Address Form appears. User fills in the form, fields are validated to be at least 3 chars long. User clicks “Save Address”. The shipping address is added to local database. User is redirected to back to list of shipping addresses.
10.3. Change default shipping address in the profile use-case: User clicks “Use as shipping address” checkbox in the list of shipping addresses in the checkout. The new shipping address is set for the order. User stays on the same screen.
10.4. Edit shipping address in the profile use-case: User clicks “Edit” link in the shipping address tile in the list of shipping addresses. User is redirected to form to edit details on shipping address. The fields are validated to be at least 3 chars long. User edits fields, clicks save, shipping address is updated in local database. User is redirected back to list of shipping addresses in the profile.
10.5. Remove shipping address in the profile use-case: User clicks “Remove” button in the list of shipping addresses in the profile. The shipping address is marked as removed from the database and according API call is made to the server. User is redirected to Add New Shipping Address Form if there is no shipping addresses left.
E-commerce App Use-Case Description
Within this task you need to do the following:
Pull all data from local database and render it on the screen.
At this time mock remote repository calls for fetching data from a local JSON file. The data structure and method names should be taken from WooCommerce REST API docs.
The text was updated successfully, but these errors were encountered: