Imagine an awesome intro here!!

Hi all, I'm pretty new to this community. So let me share a bit about myself. I'm Arun, a CS graduate, from a small town in Kerala, India. I love to build things. I found this community somehow from Github. I really don't remember how but I'm really glad to be part of this community.
Yea yea... I know you want me to get into the post asap. So here goes nothing....

Open Source Background

I'm brand new to Open Source as a contributor. I have some experience in coding as that was pretty much what I was interested in and what I enjoy.

(What?? Is it the meme? I do enjoy it even though it makes me crazy! and stop grinning )

It's really an awesome experience and feeling when you collaborate with different people and build stuffs. Collaboration first, coding second!! Some of you, who are part of EddieHub, may have thought that I just copied Eddie Jaoude(No I didn't). I'm part of an amazing community called EddieHub. They were really helpful when I first entered this forest called Open Source.

Ok, now let's move into my experience in Bug Smash!!

About This Bug

Remove extra space from readable_publish_date #13612

hadiidbouk posted on May 02, 2021

I am using the GET latest articles endpoint in my project.

The readable_publish_date property added an extra space between the day and the month, this could be fixed on the front end, but if it's a readable publish date why not be better readable

View on GitHub

The bug was really a small one. It was actually an extra space in readable_publish_date property.

How I Smashed It

I was able to smash it by tweaking the format specifier. Even though it was a small bug, this PR was a huge step for me in Open Source contributions.

Update format specifiers in readable_publish_date #13660

Arun-kc posted on May 05, 2021

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Optimization
• [ ] Documentation Update

Description

Removed extra spaces from readable_publish_date by changing format specifiers

Related Tickets & Documents

Fixes #13612

QA Instructions, Screenshots, Recordings

I'm not sure about this since the only change done is updating format specifiers

UI accessibility concerns?

N/A

Added tests?

• [ ] Yes
• [x] No, and this is why: I guess old test will still work
• [ ] I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

N/A

[optional] What gif best describes this PR or how it makes you feel?

View on GitHub

Reflection

I had a great experience by being part of this bug smash event. The community members were really helpful and encouraging. Especially rhymes, I'm really thankful for your help.

.ltag__user__id__2693 .follow-action-button { background-color: #550a61 !important; color: #ffffff !important; border-color: #550a61 !important; }

rhymes

Software developer @ Forem/DEV

As for the next steps I'm planning to explore this wild forest called Open Source more. I'm sure that I will learn a lot and meet new people through this...(hopefully )

Suggestions for DEV Community Bug Smash

I only have one thing to say to this community. Keep up the good work!!. Stumbling upon this community was such an awesome thing that happened to me this year.

Confession: Yea I did copy Eddie earlier

Cover by Eclectic People