Problem
Documentation states SQLite only requires the Database key (file path), but DbConfiguration always requires Host, Uid, Password, and Port.
Relevant code: DBTools/Core/DbConfiguration.cs (both constructors validate all keys unconditionally).
The README SQLite example works around this by supplying dummy values:
{
"Provider": "SQLite",
"Host": "localhost",
"Database": "myapp.db",
"Uid": "unused",
"Password": "unused",
"Port": "0"
}
Proposed solution
Make validation provider-aware:
| Provider |
Required keys |
| SQLite |
Database |
| Others |
Host, Database, Uid, Password, Port |
Apply the same logic in both DbConfiguration() and DbConfiguration(IConfiguration).
Acceptance criteria
Related
Docs: README.md, docs/QUICKSTART.md, docs/API_REFERENCE.md
Problem
Documentation states SQLite only requires the
Databasekey (file path), butDbConfigurationalways requiresHost,Uid,Password, andPort.Relevant code:
DBTools/Core/DbConfiguration.cs(both constructors validate all keys unconditionally).The README SQLite example works around this by supplying dummy values:
{ "Provider": "SQLite", "Host": "localhost", "Database": "myapp.db", "Uid": "unused", "Password": "unused", "Port": "0" }Proposed solution
Make validation provider-aware:
DatabaseHost,Database,Uid,Password,PortApply the same logic in both
DbConfiguration()andDbConfiguration(IConfiguration).Acceptance criteria
Provider+Databaseloads successfullyRelated
Docs:
README.md,docs/QUICKSTART.md,docs/API_REFERENCE.md