linkify all user names on ratings list; handle an account response with undefined fields

[eviljeff]

Fixes mozilla/addons#15403

Shows user account links for all ratings, and hides the fields that won't be present on the user profile page.

profile page

before

(before mozilla/addons#15402 changed the API it would have been a 404)

after

ratings

before

after

[eviljeff]

re: covecov error - I've looked but I'm not sure where I'd be adding tests, exactly (codecov claims some of the existing lines in getFormValues are covered, but can't see where). The changes in getFormValues were only added to stop Flow from complaining about the values being potentially undefined anyway - in reality your own account response will always contain those object keys, as now.

[eviljeff]

Note, the amo api on dev and stage is supposed to be returning an account response that includes all the fields, so it shouldn't be possible to test this with yarn amo:dev, but good news! (as I write) the API_GATE isn't working 🙃 .

[diox]

re: covecov error - I've looked but I'm not sure where I'd be adding tests, exactly (codecov claims some of the existing lines in getFormValues are covered, but can't see where). The changes in getFormValues were only added to stop Flow from complaining about the values being potentially undefined anyway - in reality your own account response will always contain those object keys, as now.

AFAICT you have no tests that simulate biography, occupation, location, homepage etc being undefined when going through UserProfileEdit page. All tests in TestUserProfileEdit.js use createUserAccountResponse() either directly or through dispatchSignInActionsWithStore(), without setting those fields to undefined, so they get the defaults defined in that function. So I'd say codecov complaining about lack of coverage here is warranted.

[diox]

On top of my comment about coverage...

I'm currently seeing, with dev API:

Which doesn't match your "after" screenshot.

[eviljeff]

The after is what it will look like once the shim is disabled for v5 - with the shim enabled some of the fields are still returned.

i think I'll disable the shim for v5 (different ticket) and update when that's live