Yonghwan SO

Great idea! It sounds good to me. Let me review the change in the morning. (No worries, I believe it's your own personal contribution to make us all happy :-)

Yeah, I think @breml's approach is nice since the Model layer can be slimmer and can stay focused on the database-specific jobs. I think there are many different kinds of...

Indeed, it seems like there is something that can be improved on the doc (and/or API). Anyway, I am closing this issue since it was answered and is not active...

The first step was just finished without a big issue. the next step will be performed soon. As a side note, the testing for the buffalo core was not successful...

> @sio4 Should updates to Dockerfiles go here? Ah, I will add the step! Missed during writing the OP.

Step 3: manual application-level test with a new sample application and/or an existing application - tested with a new app generated with the 0.18.5 version of CLI with go1.18.2 -...

By the way, IMO, I would like to keep the code compatible with 1.16 for a while (I mean we don't need to proactively remove compatibility code) since I think...

@paganotoni Yeah, I totally agree that we should focus on what we can do. Supporting older versions could not be a thing we can do continuously. However, what I wanted...

The root cause of this issue was just addressed in https://github.com/gobuffalo/flect/pull/60 applying it to the stack is on the work. (duplicated issue: https://github.com/gobuffalo/flect/issues/12)

Now it works find. closeing.