[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
Describe the feature
dbt sometimes raises warnings at parse time, such as tests that reference missing relations, or model configuration nodes in dbt_project.yml that refer to folders that do not exist.
On subsequent invocations, if parsing steps are skipped because partial parsing is used, then these warnings aren't re-raised, which gives the false impression that the condition that caused the warning has been resolved, when in fact the warning condition still exists.
dbt should raise parsing-related warnings on all invocations even if partial parsing means that parsing was skipped.
Is this your first time submitting a feature request?
Describe the feature
dbt sometimes raises warnings at parse time, such as tests that reference missing relations, or model configuration nodes in dbt_project.yml that refer to folders that do not exist.
On subsequent invocations, if parsing steps are skipped because partial parsing is used, then these warnings aren't re-raised, which gives the false impression that the condition that caused the warning has been resolved, when in fact the warning condition still exists.
dbt should raise parsing-related warnings on all invocations even if partial parsing means that parsing was skipped.
Describe alternatives you've considered
No response
Who will this benefit?
Anyone who encounters a parsing-related warning in dbt and is confused about why the warning message is inconsistent (see for example https://getdbt.slack.com/archives/CBSQTAPLG/p1718056852222639)
Are you interested in contributing this feature?
No
Anything else?
No response