For doctrine it would mean that factory would not force orm_default, but this could be configurable. And maybe other storage's could use some options if any.

would be nice at least with this:

• How to create collections
• How to add settings and what options available
• How to create custom providers
• How to create custom types

needs basic setting types:

• string
• integer
• boolean (Has to many possible implementations. So it can be added as custom type.)
• float
• in_array
• regex

This will be BC so it is important to be implemented in 1.0.0 version

in src/Entity/Setting.php, line 12

The @Doctrine\ORM\Mapping\Entity annotation looks like a class annotation which resolves to the Svycka\Settings\Entity\Doctrine\ORM\Mapping\Entity class which PHP does not seem to be able to autoload.

 * @Doctrine\ORM\Mapping\Table(name="svycka_settings", options={"collate"="utf8mb4_unicode_ci", "charset"="utf8mb4"})
 *
 * @author Vytautas Stankus <[email protected]>
 * @license MIT
 */
class Setting implements SettingInterface
{
    /**
     * @var int
     * @Doctrine\ORM\Mapping\Id
     * @Doctrine\ORM\Mapping\Column(type="integer", name="id")

Posted from SensioLabsInsight

no stable release until at least 70% coverage