Conversation
syphar
force-pushed
the
std-replacements
branch
from
September 22, 2026 11:37
81e9fca to
13fa455
Compare
This comment has been minimized.
This comment has been minimized.
syphar
force-pushed
the
std-replacements
branch
from
September 23, 2026 21:18
9f97c6a to
a12b6cd
Compare
Member
Author
|
This is how crates.io renders the same warning: Generally I feel like I want to find a way that we don't have to make the topbar bigger. But not sure if this is worth a dropdown? or detail page like for the abnormalities? |
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
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.

TODO
summary
Here we start showing crate warnings in the topbar.
First is the std-replacement data.
We're using a small partial so we can cache it independently from the rustdoc content.
For now, CDN caching is just a TTL of 10 minutes, with room for improvement.
We load the data from the json endpoint, which is properly cached through github pages.
For now we just run a scheduled task that updates the data every hour, happy to change the frequency.
first UI draft
First draft of the rendering, happy to take ideas? or help?
next steps
Idea is that I'll add rustsec "unmaintained" warnings as next thing, because they are relatively easy to interpret and also fit into the "crate warning" logic. In my mind I would show a second widget in the topbar if both warnings are raised by the same crate.