How I Submitted My First WordPress Core Patch (And What I Learned)
Kunal Pareek shares his experience of submitting his first patch to the WordPress core. He discovered that contributing is more accessible than he initially thought, despite the challenges involved. The article details his process of finding a suitable ticket, understanding the code, and implementing a fix for a REST API issue.
- ▪Pareek initially believed that contributing to WordPress core was only for experienced developers.
- ▪He found a suitable ticket related to a REST API issue that had been untouched for four years.
- ▪After analyzing the code, he successfully implemented a fix and generated a patch file.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3934854) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Kunal Pareek Posted on May 17 How I Submitted My First WordPress Core Patch (And What I Learned) #wordpress #php #webdev #opensource I always assumed contributing to WordPress core was for people with decades of open source experience. Senior engineers. People whose names you recognize in commit logs. Turns out I was wrong. I submitted my first patch this week and the process was more straightforward than I expected. Not easy — but straightforward. Here is exactly what I did.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
