What?
When dab init is run, update its behavior to default runtime.rest.request-body-strict to false in the generated config. This will allow REST request bodies to accept and ignore additional fields by default, making development smoother and reducing unexpected errors.
Why?
Currently, dab init in the CLI generates a dab-config.json where the runtime.rest.request-body-strict option defaults to true (strict mode). This means all extraneous/unmapped fields in REST request bodies are rejected by default, including keys. This can cause confusion for new users and adds friction for modern scenarios where flexible request bodies are preferred, especially with C# developers.
What?
When
dab initis run, update its behavior to defaultruntime.rest.request-body-stricttofalsein the generated config. This will allow REST request bodies to accept and ignore additional fields by default, making development smoother and reducing unexpected errors.Why?
Currently,
dab initin the CLI generates adab-config.jsonwhere theruntime.rest.request-body-strictoption defaults totrue(strict mode). This means all extraneous/unmapped fields in REST request bodies are rejected by default, including keys. This can cause confusion for new users and adds friction for modern scenarios where flexible request bodies are preferred, especially with C# developers.