fix(catalog): clarify listing attribution#106
Merged
Conversation
Signed-off-by: Justin Levine <20596508+jal-co@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Listed by @creator on Mon D, YYYYon component and tool detail pagesWhy
Profiles and attribution should describe every listing kind, not only components, and visitors should see when a listing became public.
How
Catalog records expose a deterministic UTC
listedAtdate using the latest public review timestamp, with submission/creation fallback. A shared formatter keeps SSR and hydration output stable.Testing
pnpm --filter web typecheckpnpm --filter web test(83 passed)pnpm --filter web buildpnpm --filter web build-storybookgit diff --checkListed by @justin on Jul 15, 20261 Listing, no1 Component, and no horizontal overflowScreenshots
/tmp/profile-listing-count.png