{"id":2624,"date":"2023-01-16T18:28:39","date_gmt":"2023-01-16T21:28:39","guid":{"rendered":"https:\/\/felipeelia.com.br\/?p=2624"},"modified":"2023-01-18T09:24:06","modified_gmt":"2023-01-18T12:24:06","slug":"deprecated-code-in-open-source-with-wordpress-functions","status":"publish","type":"post","link":"https:\/\/felipeelia.dev\/deprecated-code-in-open-source-with-wordpress-functions\/","title":{"rendered":"Deprecated code in Open Source (with WordPress functions)"},"content":{"rendered":"\n

Keeping a codebase organized always requires some changes: functions, files, structures, everything someday needs a new name or place. How do we make a change without breaking anything?<\/strong><\/p>\n\n\n\n

Open-source codebases come with several advantages but some specific challenges. Different from a service that simply provides a more strict API, like a REST API, for example, others can call almost anything in your code<\/strong>. That said, you must be cautious even while renaming the simplest function.<\/p>\n\n\n\n

Although all this can sound painful, it is not. Keeping your codebase organized is worth it!<\/strong><\/p>\n\n\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\tTable of Contents\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
  1. Make the change in phases<\/a>