https://github.com/codelytv/refactoring-code_smells-design_patterns

♻️ Example projects illustrating Code Smells in order to apply Refactoring techniques
https://github.com/codelytv/refactoring-code_smells-design_patterns

clean-code code-smells design-patterns java javascript kotlin php refactoring refactoring-exercise refactoring-kata refactorings typescrit

Last synced: 3 days ago
JSON representation

♻️ Example projects illustrating Code Smells in order to apply Refactoring techniques

• Host: GitHub
• URL: https://github.com/codelytv/refactoring-code_smells-design_patterns
• Owner: CodelyTV
• Created: 2020-09-17T09:39:40.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2024-08-17T17:39:21.000Z (5 months ago)
• Last Synced: 2024-12-21T05:03:52.416Z (10 days ago)
• Topics: clean-code, code-smells, design-patterns, java, javascript, kotlin, php, refactoring, refactoring-exercise, refactoring-kata, refactorings, typescrit
• Language: PHP
• Homepage: https://codely.tv/pro/cursos
• Size: 4.64 MB
• Stars: 570
• Watchers: 10
• Forks: 134
• Open Issues: 12
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        


  

    

  





  Refactoring from Code Smells to Clean Code

  


  🧼💩 🔜 🌈🦄





    

    





  Showcase of the refactorings and code smells catalog illustrated with practical examples in different programming languages.

  


  


  🎥 View refactoring course

  ·

  ⭐ Star this repository

  ·

  ☝️ Propose an example



## 🧠 Concepts 

### 💩 Code Smells

These are what we could consider as potential bad practices. Things such as long methods, nested conditionals, feature envy, and so on 😊

The different Code Smells are grouped based on the following taxonomy ([source](https://mmantyla.github.io/BadCodeSmellsTaxonomy)) where you will find each one of the single examples:

* Bloaters: Something that has grown so large that it cannot be effectively handled

* Object-Orientation Abusers: Solutions that does not fully exploit the possibilities of object-oriented design

* Change Preventers: hinder changing or further developing the software

* Dispensables: Something unnecessary that should be removed from the source code

* Couplers: Promotes coupling (knowledge particularities) between different classes

### 🧼 Refactorings

👷‍ Work in progress

### 🌈 Examples

👷‍ Work in progress

## 🤯 How to explore this repository

You have the following 3 main folders:

* 💩 Code Smells

* 🧼 Refactorings

* 🌈 Examples

The purpose of this repository is to illustrate with some _🌈 Examples_ how we can detect _💩 Code Smells_ and evolve a specific code applying _🧼 Refactorings_ technics.

That is the reason why the code will always be located in the _🌈 Examples_ folder with a folder for each of its possible evolutions, and linked from the _💩 Code Smells_ and _🧼 Refactorings_ directories using symbolic links.

## 👌 Examples completeness

The examples you will find in this repository are completely operational projects that you can open up in your IDE and start refactoring executing the provided test suite.

That is, we understand that in order to have a better learning experience, you must have the whole picture of the specific code snippet you actually want to analyze. This gives you the freedom to modify it right away after cloning this project without having to worry about _boilerplaty aspects_.

## 🤝 Contributing

Feel free to open an issue explaining how you want to contribute before starting out coding and we will help you figuring out the best way to approach it 😊