Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

jeffwheeless
Copy link

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.

… emojis that are being returned as strings
const 🍽️ = 416;
const 😐 = 417;
const 🤓 = 418;
const ✨ = 421;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is 420?

Copy link
Author

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

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.

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🍁

@iansltx
Copy link

iansltx commented Mar 31, 2019

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️⃣
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

@jeffwheeless
Copy link
Author

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.

👩‍🏫💬🤔💭, 😆👍. 👷📤

@Crell
Copy link

Crell commented Apr 1, 2019

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 🥇

@shadowhand
Copy link

@Crell certainly you meant 🅱️C ?

@Crell
Copy link

Crell commented Apr 1, 2019

I most certainly do. 😄 I was trying to find a stone-age emoji of some kind but came up 🤷‍♂️

@shadowhand
Copy link

🗿 ? The only "stone age" emoji I could find in 30 seconds.

@jeffwheeless
Copy link
Author

too many conflicts to resolve; closing PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants