Open frekvent-szabolcs opened 1 month ago
Hi team,
This seems like a MAJOR breaking change for anyone using DAB in development. This issue is a month old. The documentation clearly states that configuration works like appSettings, and that a base configuration can be combined with an environment specific configuration. This is completely broken.
Any update on when a fix for this breaking change will be resolved?
What happened?
I have two configuration files:
In the
dab-config.json
I defined the entities and in thedab-config.Development.json
file I defined the database connection string and set the authentication toIf I do not define the entities object in the development file. I get an error during startup:
If I define the entities as
"entities": {}
, DAB can start, but the graphql schema will not be available.If I define a single entity inside the development config file, only that specific entity will be available for queries. This way, I have to define every entity in both the development and the "live" configuration.
Version
1.1.7
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI), Custom Docker host
Which API approach are you accessing DAB through?
REST, GraphQL
Relevant log output
No response
Code of Conduct