You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest schema for dbt_project.yaml doesn't have additionalProperties: false set for its top-level flags key. This means that if you make a typo on a flag name, your dbt_project.yaml will still pass JSON schema validation. Ask me how I know 😅
I'm happy to open a PR to fix this, but wanted to make sure that it's not intentional first, since additionalProperties: false is being used elsewhere in that schema.
The text was updated successfully, but these errors were encountered:
Ooof! What did you typo? In addition to fleshing out the list of accepted flags on the schema, I've also noted that we should capture typos in dbt_project.yml when we take on dbt-labs/dbt-core#8942
I think that there's some flags we don't have enumerated here yet (especially new behaviour change flags), so before disallowing additionalProperties those would also need to be synced up. But once they're in sync I'd have no issue with locking it down!
The latest schema for dbt_project.yaml doesn't have
additionalProperties: false
set for its top-levelflags
key. This means that if you make a typo on a flag name, yourdbt_project.yaml
will still pass JSON schema validation. Ask me how I know 😅I'm happy to open a PR to fix this, but wanted to make sure that it's not intentional first, since
additionalProperties: false
is being used elsewhere in that schema.The text was updated successfully, but these errors were encountered: