Skip to content

support PersonLink elements without a separate displayName

Administratorrequested to merge
support-user-PersonLink into master

Created by: sqs

Low priority

This makes it possible to render a <PersonLink /> when all you have is a GQL.IUser. There is no good reason for requiring a displayName. The only reason it was required was to avoid a case where the component's API implied that you could render it with neither a displayName nor a user. The new component API prevents that.

Merge request reports