When we posted the Solidus community roadmap, we left technical conversations off the table. Now in this post, we'd like to focus on them. We'll discuss specific technical accomplishments and plans for Solidus 2.4 and 2.5 from a very technical perspective.
Six years ago Radar re-wrote the Spree API in RABL. Since then, the ecosystem has evolved and Rails adopted JBuilder as the default JSON API format. While RABL was an excellent choice at the time, it was no longer widely used outside our community. John Hawthorn has written a translation engine to convert our RABL templates into JBuilder templates, a long-standing request in the Solidus ecosystem. It is included in the current v2.4 Solidus release.
Spree 2.0 introduced an overhauled shipping system to allow multiple shipments. The intricacies involved in estimation and splitting of shipments created a very complex and hard-to-understand shipping API. The Spree 2.0 shipping system has been tweaked over the years, but remains largely unchanged. Since that release, the community has built dozens of gems to extend that system. Our understanding of the requirements for modern stores has both evolved and become more refined. Because of this, we’ve pushed the Spree 2.0 behavior into an extension. We will continue to support it, but recommend stores migrate to the simpler, more customizable splitting system introduced in September.
With the announcement that PhantomJS has been deprecated in favor of Headless Chrome, the writing has been on the wall for our feature spec headless browser. John Hawthorn took it upon himself to bump our webdriver to Headless Chrome for a more reliable and future proof testing solution. This should divorce the Solidus feature spec suite from any PhantomJS quirks, and provide a closer representation of each store’s usage. Based on our experience and findings, we recommend anyone using Solidus also consider the switch.
When we decided on Bootstrap for the admin, Bootstrap 3.x was the most recent official release, but the 4.0 alpha looked very promising and laid out a clear direction for the future of Bootstrap. To be as forward-compatible and store-friendly as possible, we decided to adapt the 4.0 alpha, and now in Solidus 2.4 have bumped the admin Bootstrap version to 4.0 beta2. The Solidus admin is now up-to-date and while some stores upgrading from Solidus 2.x may have minor issues, they should be easy to fix.
On Wednesday, October 4th, the Solidus core team members put aside a day to tackle the ever-growing number of open issues and unmerged PR’s in the Solidus project. Some issues were closed outright for staleness, but with some assistance from the community we were able to merge 17 PRs to make a serious dent in the outstanding number. The core team has an internal goal to speed up the feedback cycles on issues and pull requests to get them merged or closed quicker.
Since the earliest releases of Solidus, image uploading and display was handled by
has_attached_file and Paperclip. As web apps have evolved, our file and image management needs and options have as well.
Thoughtbot announced Paperclip is in a semi-official state of non-maintenance in October.
Tying Solidus to a single file upload library, and one that is very likely to be unmaintained in the near future, does not seem to be an ideal situation going forward. Forcing Solidus users to use any single file management system is restrictive. Pulling Paperclip out of Solidus into an extension makes room for custom implementations, and also gets rid of the ImageMagick dependency for Solidus itself.
Solidus inherited Spree’s ActionMailer-based notification system, which sends transactional emails at certain points of the order lifecycle. In recent years, other notification channels and methodologies have become much more popular. ActionMailer has lost ground to email service providers that provide GUI-driven JSON-based templating, A/B testing, and analytics. Customers have started requesting SMS or other non-email notification delivery. To better support the numerous ways our stores communicate with our clients and partners, we’re looking at revamping our internal API to be more flexible and robust for stores to configure its notification touchpoints.
After a couple of different directions that didn't work out, they hit on a solution with an event bus architecture. We’re incredibly excited to finally tackle and fix such a frequent headache for stores running Solidus.
As with all our posts, anyone looking for more information about any of the topics mentioned above is welcome to shoot us an email or start a conversation in the Slack #solidus channel. As a project, we value and heavily weigh the feedback we get from stores, developers, and agencies that reach out.
Join the Solidus user testing mailing list to share your opinions and participate in user testing.