For anyone interested in contributing to the DEV Community codebase, here are a few bugs that could use some love. One issue is as early as #96! (we're in the 800s now 😱)
If anything is unclear or you need feedback/help please don't hesitate to mention anyone on the core team.
YAML Errors for metadata aren't clear
#96
BUG
Current Behavior
When there's a parsing error in a new post's metadata, the returned error doesn't offer any specifics or guidance.
Expected Behavior
A more useful error message: "Title and description strings with special characters should be wrapped in quotes"
Additional Info (steps to replicate, device/browser, helpful links)
Add a title or description that uses a colon : and is not wrapped in quotes.
Screenshots
NaN in heart/unicorn/bookmark count in a post
#208
BUG
Current Behavior
When I click heart/unicorn/bookmark repeatedly(laggy internet connection), I get NaN in the counts.
Expected Behavior
When I click heart/unicorn/bookmark repeatedly, number should increase and decrease by 1 alternately.
Additional Info (steps to replicate, device/browser, helpful links)
Probably this happens, when the user clicks the icon again before the async request returns for each click (can happen with slow internet).
Screenshots
Glitch embed: full screen button not working
#253
BUG (minor)
Current Behavior
Click or tap over the Glitch embed full-screen button does nothing.
Expected Behavior
Open the full-screen Glitch.
Mixture of irrelevant posts on the profile page.
#525
Bug Report
I was scrolling through the feed, and went to the profile's page, and saw the weird list of posts. This behaviour occurred a few months back. I tried to reproduce, but it didn't happen again.
Current Behavior
I clicked on the user's profile and scrolled through his/her profile. Once you reload the page, all the irrelevant posts to his/her profile are gone. This behaviour is hard to reproduce.
Steps to reproduce -
- Open dev.to
- As soon as the page opens, click on the profile icon.
- Scroll the profile page. You are most likely to reproduce this behaviour.
Expected Behavior
User's profile should contain his/her posts.
Mobile & Desktop Screenshots/Recordings
When I clicked on the profile, I saw this -
After a reload, it was auto-fixed -
(PS. Sorry for the poor quality of the first screenshot.)
I received multiple "confirm email address" emails when I signed up
#424
Bug Report
Current Behavior
Upon signup, I received 15 "confirm email address" emails.
Expected Behavior
I should only have received one email.
Mobile & Desktop Screenshots/Recordings
Additional Info (device/browser, helpful links)
Only the final email sent (the top one in the screenshot) had the correct link. All others led me to a page with this error message:
Medium RSS feed articles are not pulled in if they have Giphy embeds
#640
Bug Report
Current Behavior
When pulling articles via RSS feed and from Medium specifically, the posts with Giphy embeds are not created because they run into an error here: https://github.com/thepracticaldev/dev.to/blob/9e35b25ac1471fad4497d3c25c974acf590de256/app/labor/rss_reader.rb#L126-L143
In line 133, open fails:
# possible_link is https://medium.com/some-long-link-that-redirects-to-the-proper-place/href
open(possible_link)
#=> RunTimeError: redirection forbidden:
#=> "gph.is/short-code-url" -> "http://giphy.com/gif-link"
Basically, the short link redirects to regular HTTP, and that isn't allowed with open.
Proposed Solutions
From easiest to hardest, we can:
- have better link checking,
- maybe try something else instead
open, - support Giphy embeds.
Additional Notes
This is not a critical issue that affects many people since I don't imagine Giphy embeds are used all that much. Also, only the articles that do have Giphy embeds are affected; the RssReader will still attempt to pull in the rest of the articles.
Colon in description text does not have proper error handling
#625
Bug Report
Leaving a colon in description text of the front matter does not have proper error handling.
Current Behavior
In this example:
---
title: Minimal bug example
published: false
description: this is: okay
tags:
---
Clicking "Preview" or "Save" will cause the page to 500 instead of having a proper error message.
Expected Behavior
We give a proper error message and not have the page hit a 500 error.
Related Files
See markdown_parser.rb.
Thanks @nestedsoftware for reporting this!
Disallow buttons with the same color as the background color
#735
Feature Request or Task
Would you check when the follow button is the same color as background thus hiding the button?
As an example, Pierre Baron on https://dev.to/prbaron has following profile page, making it hard to follow.
And the button is actually there.
Happy Coding!
Top comments (9)
Hi Jess, this is great!
On a side note: do you think issues should be assigned to the people who claim them? I saw a few comments of people asking if they could work on this or that. This way there is a mostly formal way to know who's doing what.
This doesn't mean that a third party can't give it a shot anyway but at least with a quick glance at the sidebar one can know there's someone else hard at work on the issue.
I agree with this. We've been a bit vague and uncertain about how we use assignments so far, but we could make this how we use assignments.
@jess thoughts?
That's actually something @maestromac and I tried playing with a few weeks ago, but it didn't seem like an option for us to assign anyone unless they are a project collaborator or the person who wrote the issue. We might just be missing something in the settings so I'll revisit this 😅
This is an amazing way to call out issues for the community to take a look at!
This is so helpful, I was digging through the issues on the repo, but didn't want to step on anyone's toes. My goal is to get at least one PR in to Dev.to for Hacktoberfest! :)
Coming for these once I'm through with my current task...
Awesome!
Bug Hunting Season is on!
Oh nice way to get em done. Add hacktoberfest label on em. 🙌