Skip to content

Releases: spryker-sdk/spryk

0.1.1

14 Mar 13:13
e14819d

Choose a tag to compare

Included commits: 0.1.0...0.1.1

Bugfixes

This patch will update some templates to be used for generating files. The composer.json now contains by default spryker/kernel in require, spryker/code-sniffer and spryker/testify in require-dev. The codeception.yml now uses the psr-4 namespace for PHPUnit. The generated *DependencyProvider contains now the @method annotation for the getConfig() method.

0.1.0

18 Feb 17:12
69cbd68

Choose a tag to compare

Included commits: https://github.com/spryker-sdk/spryk/tree/0.1.0

Initial Release

Spryks are some sort of code generators for Spryker. Writing code is often a very repetitive task and you often need to write a lot code just to follow Spryker's clean and complex architecture. To take a way the monkey work from writing wir up code and move faster towards writing business code Spryks are born.

Spryks are written with the help of yml files. The filename of the yml file represents also the Spryk name. In most cases the Spryk yml contains arguments which are needed to fullfill the Spryk build run. Almost all Spryks need the module name to run properly. Some Spryks require much more arguments.

The vast majority of the Spryks need to execute other Spryks before the called Spryk can run. For example Add a Zed Business Facade needs to have a properly created module before the Facade itself can be created. Therefore Spryks have pre and post Spryks and with the call of one Spryk many things can and will be created for you.