Resolves #4968
Impact: minor
Type: bugfix

Issue

When updating an address via the updateAccountAddressBookEntry, the Accounts record's updatedAt field is updated. This isn't happening when adding an address via the addAccountAddressBookEntry mutation.

Solution

The solution is to set updatedAt to the current date when adding the address. After discussing with @aldeed, I also removed logic that added the address as the only address in the matching users collection record, and logic that set the name on the address as the account's name. From Eric:

I’d actually prefer to stop storing most things, including addresses, in the users collection since we use Accounts collection for all of that. We should be gradually reducing users to being only IDP data since we hope to eventually stop using Meteor for identity.

I’d like to get rid of auto-updating the name, too. It’s always been weird that we do that since the name they put on the address might not even be their name

Breaking changes

None

Testing

1. Add an address to your account. In Starterkit, you can do that with this PR
2. Confirm the address is still added to Accounts.addressBook[] and Accounts.updatedAt is updated