Skip to main content
Code Review

Return to Answer

added 4 characters in body
Source Link
Billal Begueradj
Billal Begueradj
  • 3.4k
  • 10
  • 25
  • 34

From the outset the code looks ok. I would leave the Change and Query methods inside the class. 

If the class does get abit too much then partial the class into sensible files. Also, as a side note, look up SOLID it will help you to break down and structure your code if appropriate.

From the outset the code looks ok. I would leave the Change and Query methods inside the class. If the class does get abit too much then partial the class into sensible files. Also, as a side note, look up SOLID it will help you to break down and structure your code if appropriate.

From the outset the code looks ok. I would leave the Change and Query methods inside the class. 

If the class does get abit too much then partial the class into sensible files. Also, as a side note, look up SOLID it will help you to break down and structure your code if appropriate.

Source Link
Geek
Geek
  • 439
  • 2
  • 6

From the outset the code looks ok. I would leave the Change and Query methods inside the class. If the class does get abit too much then partial the class into sensible files. Also, as a side note, look up SOLID it will help you to break down and structure your code if appropriate.