-
-
Notifications
You must be signed in to change notification settings - Fork 688
feat: parse parameter decorators for transforms #3001
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
Open
jtenner
wants to merge
9
commits into
AssemblyScript:main
Choose a base branch
from
jtenner:parse-parameter-decorators
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2173a84
Parse and preserve parameter decorators
jtenner 9cf0769
Reject surviving parameter decorators after transforms
jtenner cac365b
Cover transform-time removal of parameter decorators
jtenner 1103856
Clarify transform-only parameter decorator contract
jtenner 0d59a95
Document transform hook timing for parameter decorators
jtenner 4786023
Fix lint for parameter decorator fixtures
jtenner bd029c6
chore: ignore AS parameter decorator fixture in eslint
jtenner 2b84dc5
Fix parameter decorator review feedback
jtenner 03925af
chore: remove legacy eslint config
jtenner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -181,9 +181,12 @@ export abstract class Node { | |||||
| name: IdentifierExpression, | ||||||
| type: TypeNode, | ||||||
| initializer: Expression | null, | ||||||
| range: Range | ||||||
| range: Range, | ||||||
| decorators: DecoratorNode[] | null = null | ||||||
| ): ParameterNode { | ||||||
|
Comment on lines
-184
to
186
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think range should be always at end. decorators: DecoratorNode[] | null,
range: Range,
): ParameterNode {And yes, this will lead to more refactorings |
||||||
| return new ParameterNode(parameterKind, name, type, initializer, range); | ||||||
| let parameter = new ParameterNode(parameterKind, name, type, initializer, range); | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar here.
Suggested change
|
||||||
| parameter.decorators = decorators; | ||||||
| return parameter; | ||||||
| } | ||||||
|
|
||||||
| // special | ||||||
|
|
@@ -926,6 +929,9 @@ export class FunctionTypeNode extends TypeNode { | |||||
| ) { | ||||||
| super(NodeKind.FunctionType, isNullable, range); | ||||||
| } | ||||||
|
|
||||||
| /** Decorators on an explicit `this` parameter, if any, preserved for transforms. */ | ||||||
| explicitThisDecorators: DecoratorNode[] | null = null; | ||||||
| } | ||||||
|
|
||||||
| /** Represents a type parameter. */ | ||||||
|
|
@@ -971,6 +977,8 @@ export class ParameterNode extends Node { | |||||
| super(NodeKind.Parameter, range); | ||||||
| } | ||||||
|
|
||||||
| /** Decorators, if any, preserved so transforms can rewrite them before validation. */ | ||||||
| decorators: DecoratorNode[] | null = null; | ||||||
| /** Implicit field declaration, if applicable. */ | ||||||
| implicitFieldDeclaration: FieldDeclaration | null = null; | ||||||
| /** Common flags indicating specific traits. */ | ||||||
|
|
||||||
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
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
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
Oops, something went wrong.
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.
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.
i prefer to put range at the end like the other ast.
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, I agree