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

Update spec for resource conditions #966

Merged
merged 1 commit into from
Nov 22, 2020

Conversation

shenglol
Copy link
Contributor

No description provided.

@codecov-io
Copy link

codecov-io commented Nov 21, 2020

Codecov Report

Merging #966 (5ba1c1c) into main (fa6e2c5) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #966   +/-   ##
=======================================
  Coverage   94.33%   94.33%           
=======================================
  Files         316      316           
  Lines       14771    14771           
  Branches       12       12           
=======================================
  Hits        13934    13934           
  Misses        837      837           
Flag Coverage Δ
dotnet 94.93% <ø> (ø)
typescript 25.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

```
param deployZone bool

resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' when (deployZone) = {
resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = if (deployZone) {
Copy link
Member

Choose a reason for hiding this comment

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

We never clarified it in the previous version of the spec, but are we making parentheses required?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question...I don't think they are needed. We don't uses parentheses for list comprehensions, so it might be better to keep them consistent. What do you think?

Copy link
Member

Choose a reason for hiding this comment

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

Personally I vote to require them - just because I feel like it'll seem more familiar to anyone used to C-style languages. We could technically relax this in the future if there's a good case for it. Going from non-required -> required would be a breaking change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Going from non-required -> required would be a breaking change.

Good point. Let's keep the parentheses then.

@shenglol shenglol merged commit f06a94d into main Nov 22, 2020
@shenglol shenglol deleted the shenglol/update-spec-for-resource-conditions branch November 22, 2020 23:57
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.

None yet

4 participants