For internal listings, the userProfile is returned as part of the GET /api/v1/listings/{listingType}/{listingId} endpoint. In this case, a small version of the user profile should be rendered at the bottom of the listing details page, with an option to navigate their full profile showing the listings created by them.
For external listings, just the author's name and contact details (email and phone number, if present) should be rendered, along with a link to the original listing.
Definition of Done:
[x] If userProfile is present in the listing details response, render the ProfileCard component implemented in #61 at the bottom of the listing details page
[x] If userProfile is present in the listing details response, below the ProfileCard, provide a link/button which navigates the user to the author's full profile page, implemented in #117
[x] If userProfile is absent, render a simplified AuthorDetails component with the author's name, and contactInfo
[x] If originalListingUrl is present, render the link to the original listing
For internal listings, the userProfile is returned as part of the
GET /api/v1/listings/{listingType}/{listingId}endpoint. In this case, a small version of the user profile should be rendered at the bottom of the listing details page, with an option to navigate their full profile showing the listings created by them.For external listings, just the author's name and contact details (email and phone number, if present) should be rendered, along with a link to the original listing.
Definition of Done:
userProfileis present in the listing details response, render the ProfileCard component implemented in #61 at the bottom of the listing details pageuserProfileis present in the listing details response, below the ProfileCard, provide a link/button which navigates the user to the author's full profile page, implemented in #117userProfileis absent, render a simplified AuthorDetails component with the author's name, andcontactInfooriginalListingUrlis present, render the link to the original listing