Releases: jbtronics/settings-bundle
Releases · jbtronics/settings-bundle
Version 2.1.0
Version 2.1.0
New features
- Allow to customize the label and help text of sub forms for embedded forms by the new
label
anddescription
options on the#[Settings]
and#[SettingsEmbedded]
attribute. The newformOptions
option on#[SettingsEmbedded]
allows to customize rendering of certain subforms.
Bug fixes
- Fixes bug with nullable properties on lazy loaded settings in combination with twig (see issue #13).
- Fail gracefully if the required database tables for ORMStorageAdapter do not exist yet, to prevent locks when using settings as container parameters (issue #14)
Full Changelog: 2.0.2...v2.1.0
Version 2.0.2
Version 2.0.2
Bugfixes
- Fixed exception that closure is not serializable, that occured when using symfony profiler and a parameter with an envVarMapper
Version 2.0.1
Bugfixes
- Fixed dependency injection of settings classes, if they used the
SettingsTrait
.
Full Changelog: 2.0.0...2.0.1
Version 2.0.0
Version 2.0.0
New features
- Added possibility to initialize and overwrite parameter values using environment variables. This is especially useful in combination in automatic deploys, docker containers, etc. See docs for more infos.
- Added possibility to create temporary copies of settings as independent instance. That is especially useful if you want to change settings to possible invalid values without breaking the whole app and is very useful in combinations with forms. See docs for more info
Backward compatibility breaks
- All service implementations are now final. Use decoration of the interfaces to change/extend the service implementations.
- Added some new methods to
SettingsManagerInterface
and other service interfaces.
Bug fixes
- Fixed error with reserved column names on MySQL @gmurambadoro in #8
- Fixed
ORMStorageAdapter
service not available (issue #9)
Deprecations
- Passing a settings class name as string to the methods of
SettingsFormFactory
service is now deprecated.
New Contributors
- @tacman made their first contribution in #4
- @gmurambadoro made their first contribution in #8
Full Changelog: 1.1.0...2.0.0
Version 1.1.0
Version 1.1.0
New features
- Settings classes are now registered as services by default. This allows to easily retrieve a settings instance, by requesting it in constructor via dependency injection:
class ExampleService {
public function __construct(private TestSettings $settings) {
//This is equivalent to calling $settings = $settingsManager->get(TestSettings::class, lazy: true)
//The settings are lazy, meaning that they are only loaded from storage, when you access a property
if ($this->settings->myString === 'some value') {
//Do something
}
}
}
Full Changelog: 1.0.1...1.1.0
Version 1.0.1
Bugfixes
- Fix cache warm throwing an error if no settings are defined by @scottdriscoll in #3
New Contributors
- @scottdriscoll made their first contribution in #3
Full Changelog: 1.0.0...1.0.1
Version 1.0.0
Initial release