Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse the items property on config type declarations #615

Merged
merged 1 commit into from
Aug 26, 2024
Merged

Conversation

julienp
Copy link
Contributor

@julienp julienp commented Aug 21, 2024

When parsing a template, parse the items property on configuration type declarations to avoid a diagnostic for an unknown field coming from the reflection code. The config section is parsed as part of the template, but not actually used, the config validation is performed by the engine instead.

Fixes #606

@julienp julienp marked this pull request as ready for review August 21, 2024 14:59
@julienp julienp requested a review from a team as a code owner August 21, 2024 14:59
declNode

Type *StringExpr
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also need to include values here/is that even supported?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah good spotting! I think this can be arbitrarily nested, we can use ConfigParamDecl recursively here, updated the PR!

When parsing a template, parse the `items` property on configuration type declarations.

Fixes #606
@julienp julienp merged commit f20ccea into main Aug 26, 2024
5 checks passed
@julienp julienp deleted the julienp/items branch August 26, 2024 07:47
@pulumi-bot
Copy link

This PR has been shipped in release v1.10.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Encountering error/warning when attempting to use strongly typed configuration
4 participants