🐛 DEV bugs up for grabs 🐛

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.

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

image

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

NaN in all

Current Behavior

Click or tap over the Glitch embed full-screen button does nothing.

Expected Behavior

Open the full-screen Glitch.

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 –

  1. Open dev.to
  2. As soon as the page opens, click on the profile icon. this-portion
  3. 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 – full-page-with-bug

After a reload, it was auto-fixed – full-page-after-reload

(PS. Sorry for the poor quality of the first screenshot.)

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

chrome_2018-08-21_12-31-40

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:

chrome_2018-08-21_13-06-30

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:

  1. have better link checking,
  2. maybe try something else instead open,
  3. 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.

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!

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.

image


And the button is actually there. image

Happy Coding!