Hi there, wanted to ask you if you see suitable an approach of customizing solidus which would work by copying all the files in the solidus codebase to the app repo? We could then compute the difference when upgrading. I think that by using this approach we would have several advantages: • Clarity and better tracking over what changed when upgrading. It should be easy to compute a diff between Solidus codebase and the app repo • We would avoid browsing constantly two codebases, • We could copy also tests, which would bring all the solidus test coverage to the app repo, which I think now should be a big concern if you have thousands of customizations • Easier to modify. We shouldnt need decorators or prepend, just modify things. I don't have clear how we could achieve this to also apply for solidus plugins, but if we have some agreement we could think about it. Let me know your thoughts, and also if you have had similar issues, how are you tackling them. Thanks!

Have you checked out the work going into Solidus Starter Frontend? It's a different approach that aims to have the host app "own" all the frontend code in the first, leaving the backend and API customized using the conventional approaches.

Sorry, I forgot to clarify, I was focusing mainly on the backend.. we are using the fronted just for the admin

I think copying the whole repo could work - but it basically puts your team on the hook for applying any updates manually. Different tradeoffs, since using the gem still means you have to update the gem, but...

we could have an automated tool to check diffs of each file, i wanted to gather opinions on this... For me it would be more valuable to improve the test coverage and figuring out updates manually than having bugs that might cost lot of money, but yes, I suppose that for each application things might be different