-
Notifications
You must be signed in to change notification settings - Fork 156
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
WIP: recursive type unrolling prototype #4125
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spot checking, this makes sense.
@@ -69993,7 +69993,7 @@ export namespace wafv2 { | |||
/** | |||
* The part of a web request that you want AWS WAF to inspect. See Field to Match below for details. | |||
*/ | |||
fieldToMatch?: pulumi.Input<inputs.wafv2.RuleGroupRuleStatementByteMatchStatementFieldToMatch>; | |||
fieldToMatch?: pulumi.Input<inputs.wafv2.RuleGroupRuleStatementXssMatchStatementFieldToMatch>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this just better shortening? It sounds like it should be RuleGroupRuleStatementMatchStatementFieldToMatch
, since the rule statement appears in types nested from multiple properties of RuleGroupRuleStatement
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah ugh, shorter token heuristic picked this. I'd like to try to give it a better name.
Couple of problems here. tfgen is non-deterministic with substitutions like this one:
These two types should not be have been picked for rewrite I suspect, and it's strange that one or the other is picked, I'd expect A<B or B<A on these.
With
|
Preview applying pulumi/pulumi-terraform-bridge#2134