* Add a new component `account` to header, it provides a container div for its react component

* Add new `<Account>` component to main React app `react-components.js`, it renders `<AccountTrigger>` component to toggle the `<AccountDropdown>` component, two components `<SignOutLink>` and `<SignInForm>` are created for reusable purpose

* Add a new reducer to toggle open state of account dropdown

* Refactor `<SignIn>` and `<MyAccount>` components to use `<SignOutLink>` and `<SignInForm>` created for account dropdown, remove the duplicate CSS as they are existing in CSS file of `<SignInForm>`

* Fix a bug found in `<AccountLink>` component, the issue was that the `identity-obj-proxy` module used by `jest` during the test running will mock `classes` imported to `<AccountLink>`, this breaks the rendering of the `<Button>` component because it doesn't expect `classes` to be mocked, instead, it should be an imported CSS modules, so we assign imported CSS modules to an object `classes`, now the mock won't happen so the test can run correctly

* Add or update test files for `<AccountLink>`, `<MyAccount>`, `<SignOutLink>`, `<SignIn>`, and `<SignInForm>`, add generated or updated snapshots files for them as well

* Add a new component `<AccountIconText>` to display the sign in text if the user is not signed in, or display greeting text if the user has signed in, this component will be displayed next to the account icon on header of storefront

* Add corresponding translations in `account.json` i18n file

* Fix the prettier issue for `accountIconText.css`

…if-components into issues/CIF-1444

* Add 'package-info.java' to change the version to '2.0.0' as suggested by Java baseline plugin during the mvn build

* Now we can use account dropdown to reset password and create a new account
* Add 'Address Book' and 'Address Information' to dropdown, at the moment, they're dummy links, the implementations will be added in other ticket
* Add new behaviour, now after user signs in, the account dropdown will be hidden, same behaviour is applied after user signs out
* Refactor code so that components and hooks can be reused for account dropdown

* Add tests to verify the components are rendered as expected

…e '<AccountIconText>' component (#303)

* Changes the references of account component in other files

* Merge logic of '<AccountIconText>' to '<AccountContainer>', now '<AccountTrigger>' will render icon label based on 'label' property passed in

* Update test and snapshots of '<AccountContainer>' component

* Remove '<MyAccountLinks>' and '<SignOutLink>' components and move their logic back to '<MyAccount>' component because now we will reuse '<MyAccount>' in account dropdown

* Add translation string for cancel button of change password form

* Add links of address book and account information to my account so that side panel now will have them available to

* Add a new form title

* Move forgot password button to underneath the password field

* Change label of email input field

* Delete '<SignInForm>' component and merge its logic back into '<SignIn>' as now we are going to reuse it in account drop down and side panel

* Update test and snapshots

…oing to use miniaccount component to render the mount point for account dropdown

…ve the unused CSS file (#303)

…reate one React portal in '<AccountContainer>' component, rather than create two React portals in '<AccountDropdown>' and '<AccountTrigger>' respectively (#303)

…to the folder of 'AccountContainer', update the import paths in '<AccountContainer>', this change allows us to group the account dropdown related components in same place (#303)

…ere is sign-in error (#302)

* Now we only dispatch 'toggleAccountDropdown' action when the sign-in is successful

* Test if handler function of click event is called when button is clicked

…onents into CIF-1444

* Remove mock of 'ReactDOM.createPortal' from test suits of account dropdown and account trigger as this method is not used by these two components any more

* Add a new state 'accountContainerQuerySelector' in '<UserContextProvider>' to specify the DOM query selector that should be used to find the account container on header

* Add a new state 'authBarContainerQuerySelector' in '<NavigationContextProvider>' to specify the DOM query selector that should be used to find the auth bar container on navigation side panel

* Use 'prettier:fix' to fix the format issue so that it won't fail the CircleCI test

Conflicts:
	ui.apps/src/main/javascript/react-components/src/index.js

Create the "Address Book" component

* Add CREATE, UPDATE, DELETE queries

* Update customer details query to include the addresses query

… project

…tton can be passed in as a prop

* Please note now the redirect URL is hard coded due to we can't get the base URL path at the moment, this will be fixed when base URL can be retrieved from server

* Add a '<AddressItemsContainer>' component to render address items, as well as add new address button

* Add a '<AddressFormContainer>' component to render the address form

* Add corresponding state and actions in 'UserContext' to support create, query addresses

* Will continue to finish the edit and delete address features

Conflicts:
	react-components/i18n/en/account.json
	react-components/src/components/AccountContainer/accountDropdown.js
	react-components/src/context/UserContext.js
	react-components/src/index.js

* Fix the issue in the previous commit where edit and delete address features are not working properly

* Adjust the styling of address delete modal to match the design

* This is to fix the issue when creating or updating the address, the region_code can't be saved properly

* Now we can control whether or not to show 'Make my default address' check box in address form

* Clear the update address when address form is closed if it's not null

* Pass the region object rather than just region_code field when executing create and update address mutations so that region_code can be saved correctly

… changes

…dress

* Adjust padding for address book

* Set default_billing now, its value is the same as the value of default_shipping, at the moment, if default_shipping is set to true for an address, then default_billing is set to true as well

* Add logic to hide delete button if the address item is set to default shipping and billing address

…t folder

… depend on it

* Add a new prop 'heading' so that we can specify the form heading label now, change the default value of the heading to 'Address' if not specified

* Change the default label of submit button to 'Save' if not specified

* Update the involved components to support the above changes including tests and snapshots

… in address book page

* We now don't set position:absolute to form body as it will make the form body element go out the scope of its parent, which is '<form>' element in this case

* Now we can control positioning of address form component in its wrapper container instead becuase the form body element is not set to absolute position any more

…onent

* Remove the loading indicator from '<AddressFormContainer>' to keep consistent behaviour with address form in checkout side bar

* Remove the unused translation string from i18n file

* Move the styles for form error message to 'addressForm.css'

* We need to pass 'region_id' along with 'region_code' when creating or updateing an address

* Now the region id field is included in the countries graphql query so that we can get the id based on the region code when saving changes made for address

…ion id

* Extract the event handler callback function of delete button to user's actions.js

* Move the import of the delete customer address mutation to UserContext.js, define a new function that invokes delete address action and expose this function to component

* Make <AddressDeleteModal> to use the function defined in UserContext.js so the business logic will not be exposed to component level now

…Address'

…mContainer.js

* Extract the logic of 'getRegionId' and put it inside a custom hook 'useRegionId', add the test for the newly added custom hook

…region id can't be found

…ssFormContainer>' component

…Form'

…ormContainer>' to use that

…ctions

…pshots

* Refactor 'useAddressForm.js' to extract create and update address logic to two separate actions

* Fix an issue when update an address, the last name is not returned as part of the response

* Clean up the dispatch logic after successfully create or update address

…action name used in action test

… and account dropdown

…address button

…text.test.js

…e name of test suite in UserContext.test.js

… the related tests

* When an address is created or updated, the GraphQL endpoints won't accept email as a valid field thus won't save it, so we will hide email input field from address form used in address book now

* Explicitly show email input field in address form used in checkout to keep the existing feature working as expected

* Update the tests to reflect this changes

* Add one test suite to increase the test coverage rate for addressForm.js

…if-components into issues/CIF-1398

…fault address, the previous default address still has the 'Default' label applied

… coverage report