Calling Developers!
We are reenergizing our code contribution process!
Learn MoreFirstSpirit Connect for Commerce - Spryker Bridge API
@Guido X Jansen Jfi, couple of month ago we have just created this bridge API as a separat ZED API hosted via PaaS (as a private vendor package for one of our customers that is using FirstSpirit).
To be precise - Firstspirit expecting this API Standard
And all these endpoints can be configured on project level.
<?php declare(strict_types = 1); namespace Pyz\Zed\FirstSpiritApi; use ValanticSpryker\Zed\CategoryFirstSpiritApi\Communication\Plugin\CategoriesFirstSpiritApiResourcePlugin; use ValanticSpryker\Zed\CmsFirstSpiritApi\Communication\Plugin\CmsFirstSpiritApiResourcePlugin; use ValanticSpryker\Zed\FirstSpiritApi\FirstSpiritApiDependencyProvider as ValanticFirstSpiritApiDependencyProvider; use ValanticSpryker\Zed\ProductFirstSpiritApi\Communication\Plugin\ProductsFirstSpiritApiResourcePlugin; use ValanticSpryker\Zed\UrlResolverFirstSpiritApi\Communication\Plugin\LookUpFirstSpiritApiResourcePlugin; use ValanticSpryker\Zed\UrlResolverFirstSpiritApi\Communication\Plugin\StoreFrontFirstSpiritApiResourcePlugin; class FirstSpiritApiDependencyProvider extends ValanticFirstSpiritApiDependencyProvider { /** * @return array<\ValanticSpryker\Zed\FirstSpiritApi\Communication\Plugin\FirstSpiritApiResourcePluginInterface> */ protected function getApiResourcePluginCollection(): array { return [ new CategoriesFirstSpiritApiResourcePlugin(), new CmsFirstSpiritApiResourcePlugin(), new ProductsFirstSpiritApiResourcePlugin(), new LookUpFirstSpiritApiResourcePlugin(), new StoreFrontFirstSpiritApiResourcePlugin(), ]; } }
But not sure what it needs, to get this into spryker-eco.
@schoenfeld that's good to know Patrick, thx! We'll ask around to see how we can make that happen