Releases: rasuvaeff/yii3-settings-db
Releases · rasuvaeff/yii3-settings-db
Release list
v2.0.1
- Docs: the documented
setSourceNamespaces()migration registration does not
find the bundled migration and never has —yiisoft/db-migrationmatches the
PSR-4 map by string prefix and resolves into the core package, so
./yii migrate:upexits 0 having created nothing. Both READMEs now say so and
give a workingInjector-based recipe until the upstream fix ships.
v2.0.0
Breaking. See UPGRADE.md — an installation that already
applied the migration must rewrite one row in the migration table.
- The bundled migration moved to
Rasuvaeff\Yii3SettingsDb\Migration\M260605120000CreateSettingsTable
(src/Migration/, PSR-4 autoloaded) from a global class inmigrations/.
Register it withsetSourceNamespaces()instead of avendor/path. Being
autoloadable is what makes it safe to reference in DI at all: with the old
global class, adding any container definition for it made
Yiisoft\Di\Containerfatal at build time in every request, because
new ReflectionClass()ran before the migration runner had required the file. - The documented way to rename the table never worked.
M...::class => ['__construct()' => ['table' => ...]]is ignored:
yiisoft/db-migrationbuilds migrations throughInjector::make(), which
resolves arguments by name or type from the container and does not read
definitions keyed by the migration's class — and a scalarstring $tablehas
no type to resolve. Users following the README silently got the default name. - The table name is now a typed value object that
Injectorcan resolve,
built byconfig/di.phpfrom params. One source of truth: the migration and
DbSettingsProvidercannot disagree any more (in 1.x the runtime read params while the
migration used its own default, so configuring params pointed the runtime at a
table the migration had never created). - New
table_prefixparam, prepended totable— a single place to keep
package tables out of the way of an application's own. DbSettingsProvidervalidates the table name (through the same value object)
— in 1.x it interpolated whatever string it was given straight into the query
builder, with no identifier check at all.- The row mapper's integer check is anchored with
\zinstead of$: PCRE's
$also matches before a trailing newline. - Bump
rasuvaeff/property-testingto^2.6.
v1.1.1
- Add
/benchmarksand/Makefileto.gitattributesexport-ignore.
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
- Migrate test suite from PHPUnit to Testo. Internal change, no public API impact.
v1.1.0
- Console command:
ReencryptSettingsCommand(settings:reencrypt) invokes
DbSettingsProvider::reencryptSecrets()from any Symfony Console /
yiisoft/yii-consoleapplication. Requiressymfony/console ^7. - Added
getByPrefix(): singleLIKEquery resolving all defined keys with a
given prefix through the standard precedence (DB > fallback > default). - Added
setMany(): batch upsert in a transaction with upfront validation
(unknown keys throwUnknownSettingException, readonly keys throw
ReadonlySettingException); rolls back entirely on any failure.
v1.0.0
Initial release.
DbSettingsProvider: DB-backedWritableSettingsProvider+SettingsInspector
with aSettingsProviderfallback (configvalues). Implementsdescribe()
anddescribeAll().- At-rest encryption of secret settings via libsodium (XChaCha20-Poly1305),
AAD-bound to the setting key:Crypto\KeyRing,Crypto\SodiumCipher,
key rotation +reencryptSecrets(). readonlydefinitions:set()/remove()throwReadonlySettingException;
describe()reportsisWritable: false.- Yii3 config-plugin wiring (
config/di.php,config/params.php): binds
WritableSettingsProvider,SettingsProviderandSettingsInspectorto the
same instance; buildsKeyRing+SodiumCipherfrom
rasuvaeff/yii3-settings-db.cipher(key_id,key) — turnkey encryption. - Shipped migration for the
settingstable;SettingRowMapperfor typed
row (de)serialization. - Requires
rasuvaeff/yii3-settings^1.0.