Skip to content

Releases: bezumkin/vesp-core

4.5.0

29 Jan 08:51
Compare
Choose a tag to compare
  • feat: upgrade robmorgan/phinx

4.4.0

29 Jan 02:11
Compare
Choose a tag to compare

4.3.0

07 Jan 07:01
Compare
Choose a tag to compare
  • feat: relax requirements for illuminate packages

4.2.0

06 Jan 06:51
Compare
Choose a tag to compare
  • feat: ability to specify "offset" instead of "page" for get query

4.1.1

14 Nov 10:16
Compare
Choose a tag to compare
  • fix: maxLimit property processing

4.1.0

14 Aug 09:23
Compare
Choose a tag to compare

feat: move filesystem initialization away from model constructor

4.0.4

22 Jul 05:17
Compare
Choose a tag to compare

fix: do not process GIFs if specified the same format

4.0.3

14 Jul 09:43
Compare
Choose a tag to compare

fix: checking an array of scopes in controller

4.0.1

08 May 08:33
Compare
Choose a tag to compare
  • relax requirements in image controller

4.0

14 Mar 04:37
Compare
Choose a tag to compare
4.0

Controllers are now expecting for the Illuminate\Database\Capsule\Manager instance instead of Vesp\Services\Eloquent

You can manually configure this service or just register the Vesp service in the container:

<?php

require dirname(__DIR__) . '/core/bootstrap.php';

$container = new DI\Container();
$container->set(Illuminate\Database\Capsule\Manager::class, new Vesp\Services\Eloquent());

$app = DI\Bridge\Slim\Bridge::create($container);
// ...

This change makes using of vesp/core in other systems more convenient.