-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add methods properties in emoji to sidebar #67871
Conversation
emojis += if is_rustc_private { "⚙️" } else { "🔬" }; | ||
}; | ||
if item.deprecation().is_some() { | ||
emojis += "⚰️"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this better
emojis += "⚰️"; | |
emojis += "🔥"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other options to consider:
- 👎
- 🕸
- 🚨
- 🚧
- 🛑
- ⛔
- 🚫
- ❗
- ❌
- 🟡
- 🟨
- 🚩
⚠️
I'm personally partial to 🚧 (followed by 🚩). think they convey the message of "hey, pay attention, this will go away at some point" without being too strong.
EDIT: 🚧 may have too much of a "under construction, stabilizing" connotation than we would like, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, notably, MDN uses 👎 for deprecated APIs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we should bikeshed which emoji to use, right now there is not one to use. The one I suggested is a coffin. I think I prefer 👎. Can there even be a vote or something for this?
Added the screenshots. |
Co-Authored-By: lzutao <[email protected]>
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
I'm not a big fan of the rendering. The icons are too small... Also, this is quite the UI change so cc @rust-lang/rustdoc |
While I don't object to this on principle, I would prefer to see something which helps those who don't grok images. Either tooltips, or else some help somewhere to explain the iconography. |
That's my issue with icons: we have to explain them. :-/ |
I don't object to them being there so long as they're explained. tooltips would be most intuitive for people. Once they learn, the emoji will be very good from an 'at a glance' ability to recognise deprecated names etc. |
Anyway, for unsafe we already have one which looks like this: /!\ (yep, now imagine it "in picture" haha) |
What if we were to do the same to reduce the opacity of those that is unstable and add a strikethrough for those that are deprecated, like on the other methods in addition to this? |
I would be concerned that reduced opacity or strikethrough would reduce readability in the sidebar which is, to some extent, an accessibility issue. At least added emoji don't reduce the readability of the text. |
@kinnison That is also one of my concern and why I prefer emoji over that. I also tried using a big one instead of subscript, it looks very distracting that way. However, I am way more concerned with using different type of hints in different places, such as using this in sidebar, both text style and this emoji superscript in page bottom references, using weird box with some emoji and some text for the main text. Looks kinda congruent but still weird, and also the search does not include any of these, but it may be further improved. |
So here what I suggest @pickfire: I'm not a big fan of emojis but it could improve readability if done correctly. So let's open an issue where we can discuss it. When we'll reach a consensus, we can come back to this PR so you end the implementation. Sounds ok to you? (and to everyone else?) |
Yup, looks good to me. So we keep this PR open and just reuse it for later or close it and open one again if needed? |
As you prefer. Keeping this one open seems fine to me but other rust people might disagree. So I personally think it's ok. :) |
Closing it then :P |
Fix #67869