Merry Christmas, Happy Holidays all! Quick questi...
# general
c
Merry Christmas, Happy Holidays all! Quick question about long term stuff going on with the frontend. I’m currently using the old frontend, and have been implored to upgrade to “starter_frontend” because at 4.0 it will no longer be included in core (right?). But, this is confusing. What I think I want is an agnostic frontend with generalized controllers that can be prepended to for customizations. The “starter_frontend” nomenclature for this seems a bit confusing to me because the controllers shouldn’t be ‘starter’ per say, more like standard. Right? Is the most basic frontend controller logic ever going to be put into core? If I add the gem for the starter frontend, hoping to get future major updates on the controller side, and run the install generator, it’s going to overwrite all of my customizations, right? So, I’ve got to more or less rebuild the entire frontend from scratch (fresh install of Solidus with the new frontend generator) with the new gem, and then when there are controller updates I guess there will be an update generator or something? Or, is my thinking about this wrong—should I plan to be wholly responsible for frontend controller logic in the long term and just copy all the stuff over and cross reference updates as they come on?
👍 1
j
The removal of the legacy front end from core shouldn’t impact your ability to use it. I’ll try to come back maybe tomorrow and explain the situation here as you’ve got some misconceptions. The reason we’ve separated the front end and done what we’ve done is because including to front end in the core gem made it near impossible for us to make any changes to it.
❤️ 1
The starter frontend is targeted at new stores. I'm not sure if any thought has been put into the upgrade path for existing stores and I don't think that we should really accommodate that use case. It might be nice for those stores, but it could impair our ability to make further improvement to the starter frontend. The starter frontend is a starter because it generates all the frontend controllers in your application for use to use as a starting point and customize to your needs. Because the frontend was the primary thing new stores customized, and because those customizations were typically done with a lot of decorators, it made it near impossible for us to make any changes to the old frontend. Almost any change was basically guaranteed to break some store somewhere, and don't even think about touching any of the views. Who knows what people had done to those. I would recommend just sticking with solidus_frontend if that's where you're at. It's a stable platform that won't move under your feet. The effort of rebuilding your store on top of starter frontend probably won't be worth except maybe in the longest of long terms. This split was simply our solution to make it so the new frontend could be upgraded and changed without affecting existing stores. Sure, it would be nice if we could all build off a shared platform where new and existing stores alike could benefit from each new change, but in practice people simply customize their frontends too much for this to actually be possible.
❤️ 1
c
Ok, this makes total sense now! Thank you :)