├── CONTRIBUTE.md ├── README.md └── CODE_OF_CONDUCT.md /CONTRIBUTE.md: -------------------------------------------------------------------------------- 1 | # Contributing guidelines 2 | 3 | If you have suggestions for R error/emoji translations to add, please submit a pull request or add an issue. If you would like to request a translation, please add an issue. 4 | 5 | Before doing so, please review the [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. 6 | 7 | You can submit a translation with or without additional explanation, or add explanation to someone else's submission. 8 | 9 | ### Without explanation, aka `verbose = FALSE` 10 | 11 | Add your translation to the appropriate section, make sure the emojis render properly (and look the way you want them to look) on GitHub, and you're done! 12 | 13 | ### With explanation, aka `verbose = TRUE` 14 | 15 | Everything above, plus 16 | 17 | - 📦: indicate the package that the error is specifically associated with (if any), 18 | - ❓: include a brief sentence describing when users might expect to see the error (with the aim of helping those who are unfamiliar with the error), and 19 | - ✅: briefly (and generically) describe how you would debug the error. 20 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 😤 ➡️ 🤣 2 | 3 | Errors can be frustrating, but could they also be fun? 4 | 5 | This repo is inspired by a [random tweet](https://twitter.com/minebocek/status/1035377949036486656) of mine which made me realize that there are others out there who enjoy emoji puzzles. 6 | 7 | Deciphering errors can be difficult and frustrating, but maybe seeing them in emoji form would help lighten things a bit? 8 | 9 | Note that I'm not suggesting we replace R errors with emojis (that might make them even more frustrating!), but I can see a venue for these in blog posts, class notes, talks, etc. 10 | 11 | The translations are organized in two groups: 12 | 13 | - `verbose = FALSE`: without any explanation 14 | - `verbose = TRUE`: some explanation on where the error comes from, why it might be happening, and how it can be resolved 15 | 16 | If you have suggestions for R error/emoji translations to add or want to request a translation, please see the [contributing guidelines](CONTRIBUTE.md). 17 | 18 | Hello. 19 | 20 | ## Translations 21 | 22 | ### `verbose = FALSE` 23 | 24 | - 📦/📛🌌 🚚 ☹️ 25 | Package or namespace load failed 26 | 27 | - 🚶‍♂️⬅️🚪 🔱 👑 1️⃣ 28 | Exited with status 1 29 | 30 | - 💡 ⌨️ 𝍏 ❌🔪 31 | Object of type closure is not subsettable 32 | 33 | - 🗂(🗂, ®️✝️) ❌📭🖇 34 | Error in file(file, “rt”): cannot open the connection 35 | 36 | - 🌫️🏛️🔘 37 | Undefined columns selected 38 | 39 | - ❌🔢 🗣 ➡️ 0️⃣1️⃣ 👩‍⚕️ 40 | Non-numeric argument to binary operator 41 | 42 | - 🤷‍♀️💰 👍/👎 🍞 43 | Missing value where TRUE/FALSE needed 44 | 45 | - 💲👩‍⚕️🤕⚛️↗️ 46 | $ operator is invalid for atomic vectors 47 | 48 | 49 | 50 | ### `verbose = TRUE` 51 | 52 | - 💡❌🕵️‍♀️ 53 | Object not found 54 | - ❓: Object not defined in the active workspace. 55 | - ✅: If working in the console, check your environment tab, and if the object is not listed there, define it. If working in an R Markdown file, define the object prior to the code chunk resulting in this error. 56 | 57 | - 👩‍⚕️🔪 🚫 ❌ 🏃‍↔️ 📖 58 | Operation not allowed without an active reactive context 59 | - 📦: [shiny](http://shiny.rstudio.com/) 60 | - ❓: You are trying to access a "reactive" element inside the Shiny `server` function, but outside any of the reactive functions such as `renderTable()` or `renderPlot()` etc. 61 | - ✅: Wrap it inside a `reactive()` or place inside a `render*()` function. 62 | - 🗺 ❗️ 🐣 🎨 63 | ⏩ 😦 ➕ 😄 ❓ 64 | Error: mapping must be created by aes() 65 | Did you use %>% instead of +? 66 | - 📦: [ggplot2](https://ggplot2.tidyverse.org/) 67 | - ❓: You are using the pipe operator with `ggplot()` 68 | - ✅: Replace `ggplot() %>% geom_*()` with `ggplot() + geom_*()` 69 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at mine@rstudio.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | --------------------------------------------------------------------------------