2_1_0_migration_from_2_0_0

Migration from ElasticSuite 2.0.0 to ElasticSuite 2.1.0

Why is ElasticSuite 2.1.0 not backward compatible with ElasticSuite 2.0.0 ?

During the development process we realize that few things need to be fixed to match Magento 2.x development standards :

• First the composer vendor name we were previously using (smile-sa), is not compliant with the standard used in Magento since it have to match the PHP namespace we use into the code. As a result static tests will raise a lot of warning if we had not changed our vendor name from smile-sa to smile

• Second, and always regarding Magento strict policy, PHP namespaces and module name have to follow a strict policy. As a result our modules and PHP namespaces have to be renamed (notice the subtile case variation) :

  • Smile_ElasticSuite* to Smile_Elasticsuite* for the modules names
  • \Smile\ElasticSuite*\ to \Smile\Elasticuite*` for the PHP namespaces.

Renaming everything was an uneasy decision to be made since it does break backward compatibility when updating to version 2.1.0. But as the module is still in its early stages we consider it was the best decision to be taken since the number of errors raised by static testing made the module quite uncomfortable to work with.

It is an exceptional decision which concerns only version 2.1.0 of the module which is still young. Future updates will be as simple as just running composer update.

Migration to ElasticSuite 2.1. How to ?

Module install

Database fix

Code fix