-
Notifications
You must be signed in to change notification settings - Fork 20
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
Emojis as the new norm for status codes #16
Conversation
… emojis that are being returned as strings
const 🍽️ = 416; | ||
const 😐 = 417; | ||
const 🤓 = 418; | ||
const ✨ = 421; |
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.
Where is 420
?
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 couldn't think of a comparable emoji for that but I'm open to suggestion
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 think 😤 would be appropriate.
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.
☕ would be more appropriate for 418 IMO.
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.
🍁
Per SemVer constraints (and in keeping with emoji-ness), since we're renaming the source of these consts, this should be tagged as version ⒈2. Or maybe 1️⃣.2️⃣; this revises the major version number to indicate that we've embraced the wave of the future of Representational HTTP Status Transfer (REHST). |
… operational state, but is really chill about it.' Also update the readme for enhanced emojiness.
@@ -2,11 +2,11 @@ | |||
|
|||
All notable changes to this project will be documented in this file, in reverse chronological order by release. | |||
|
|||
## 1.2 - 2019-03-31 | |||
## 1️⃣.2️⃣ - 2️⃣0️⃣1️⃣9️⃣-0️⃣3️⃣-3️⃣1️⃣ |
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've taken into consideration what others have said and I feel that it is great feedback. I've made some modifications to this pull request and it should be better than it was. 👩🏫💬🤔💭, 😆👍. 👷📤 |
Wouldn't it be better for BC to keep both sets of constants side by side? That would support all 💯 current implementations while still opening up access to the 🆕 modern world. That would be 🥇 |
@Crell certainly you meant |
I most certainly do. 😄 I was trying to find a stone-age emoji of some kind but came up 🤷♂️ |
🗿 ? The only "stone age" emoji I could find in 30 seconds. |
too many conflicts to resolve; closing PR |
In light of recent revelations that have occurred within the last week ending around the start of the month of April; emojis have become the new standard for status codes. Emojis have the ability to convey the proper emotions attributed to how we see the status codes without having people remember what the particular number means. This is also helpful to end users because no longer will we get calls that a user is getting repeated 404. Instead, now they can call you and say they are getting the construction emoji and they fully understand what means.