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

[feature] export Keyword #3

Open
Vurv78 opened this issue Jan 18, 2022 · 0 comments
Open

[feature] export Keyword #3

Vurv78 opened this issue Jan 18, 2022 · 0 comments
Labels
A-Compiler Dealing with the compiler (analyzer, tokenizer, parser, transpiler) P-Low T-Feature Feature request X-Typescript Parity with Typescript

Comments

@Vurv78
Copy link
Owner

Vurv78 commented Jan 18, 2022

Is your feature request related to a problem? Please describe.
Need to be able to export created variables and functions from extensions to user chips,

Describe the solution you'd like
You could export variables in order to pass them to user chips

export const foo = 55;

Describe alternatives you've considered
Taking them from the scope, although this would be way less explicit and could lead to variable collisions

Additional context
This is needed mostly for extensions right now, since modules / imports are not a thing
This should also replace the existing auto-exporting behavior of declare, so instead of typing

declare var CLIENT: boolean;

you'd now put

export declare var CLIENT: boolean;

as you'd see in regular typescript.

@Vurv78 Vurv78 added T-Feature Feature request X-Typescript Parity with Typescript A-Compiler Dealing with the compiler (analyzer, tokenizer, parser, transpiler) labels Jan 18, 2022
@Vurv78 Vurv78 added the P-Low label Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Compiler Dealing with the compiler (analyzer, tokenizer, parser, transpiler) P-Low T-Feature Feature request X-Typescript Parity with Typescript
Projects
None yet
Development

No branches or pull requests

1 participant