henryvw / stoic_penknife Goto Github PK

See https://github.com/Henryvw/stoic_penknife/network/alerts

Remove e_ from names

Model re-naming is not easy in rails, symbols and stuff, might break in unexpected places

Research renaming Models

• Happy Path / Error Path
• Push specific error / validation cases into deeper layers

• What is important to write here?
• How do other well-written ReadMes explain their projects? What are ReadMes that I like that can give me inspiration?

Even though I won't write any more Controller Specs and will write Feature / Integration Specs, I want just one Controller Spec for Exercises.

(It's still useful to have some knowledge of Controller Specs for legacy applications)

Create "action objects" also called "service objects"... if the save method gets really complicated.

Google / research "form objects", "action objects", "service objects", "repository pattern"

Create folder structure:

models/forms/
models/views/
models/actions/or models/services/

Create classes that basically manage the forms, put all the logic there instead of in the views. These also have the advantage of being able to write unit tests.

The app doesn't really need this stuff right now, but where can I use it to practice these patterns?

• Look for accepts_nested_attributes - that would be a place to refactor into a form object