Skip to content

Conversation

pshao25
Copy link
Member

@pshao25 pshao25 commented Aug 25, 2025

As titled.

Pay attention:

  1. Do customization for partial resource.
  2. Do customization for resource data that changes order.

@Copilot Copilot AI review requested due to automatic review settings August 25, 2025 08:06
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

/// <param name="provisioningState"> The current provisioning state of the forwarding rule. This is a read-only property and any attempt to set this value will be ignored. </param>
/// <returns> A new <see cref="DnsResolver.DnsForwardingRuleData"/> instance for mocking. </returns>
[EditorBrowsable(EditorBrowsableState.Never)]
public static DnsForwardingRuleData DnsForwardingRuleData(ResourceIdentifier id, string name, ResourceType resourceType, SystemData systemData, ETag? etag, string domainName, IEnumerable<TargetDnsServer> targetDnsServers, IDictionary<string, string> metadata, DnsForwardingRuleState? dnsForwardingRuleState, DnsResolverProvisioningState? provisioningState)
Copy link
Member

Choose a reason for hiding this comment

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

we should not make all parameters to required.
We only make those parameters that shared with the other generated overload to required, others must remain optional
For instance,
previously we have: Foo(a = null, b = null, c = null, d = null)
now we have: Foo(a = null, b = null, d = null, c = null)
and now we must add back this:

Foo(a, b, d = null, c = null)

because a, b are shared parameters.

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

Successfully merging this pull request may close these issues.

2 participants