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.

Sign up for GitHub

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

Jump to bottom

Update README to allow exports before export #498

Merged
merged 2 commits into from
Mar 2, 2023
Merged

Update README to allow exports before export #498

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a5e75e
Update README to allow exports before export
robbiespeed Mar 2, 2023
2bfa62a
remove square brackets for optional default keyword
robbiespeed Mar 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ Finally, static fields are executed and applied.
This decorators proposal uses the syntax of the previous Stage 2 decorators proposal. This means that:
- Decorator expressions are restricted to a chain of variables, property access with `.` but not `[]`, and calls `()`. To use an arbitrary expression as a decorator, `@(expression)` is an escape hatch.
- Class expressions may be decorated, not just class declarations.
- Class decorators come after `export` and `default`.
- Class decorators may exclusively come before, or after, `export`/`export default`.

There is no special syntax for defining decorators; any function can be applied as a decorator.

Expand Down