Require a semicolon after augment decorator statements#2343
Merged
Conversation
daviwil
requested review from
allenjzhang,
bterlson,
markcowl and
timotheeguerin
as code owners
August 30, 2023 13:20
Contributor
|
Changes in this PR will be published to the following url to try(check status of TypeSpec Pull Request Try It pipeline for publish status): Website: https://cadlwebsite.z1.web.core.windows.net/prs/2343/ |
daviwil
force-pushed
the
augment-statement-semicolon
branch
from
August 30, 2023 13:33
37d70c7 to
c91d4b3
Compare
timotheeguerin
approved these changes
Sep 5, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes #2059 by requiring that a semicolon appear after an augment decorator statement. This is a breaking change but it should be mitigated by the fact that the TypeSpec formatter already adds a semicolon for all augment decorator statements.