-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
Changing source file extension #719
Comments
The |
I think you can make it kind of work in VS Code: First, set file association settings like so:
Then instead of relying on
|
Iirc correctly it used to be more complicated than that, perhaps because For a bit of additional background: My stance on this so far was to delay this until there's a dedicated language service for AssemblyScript, which in turn is likely to allow picking whatever file extension(s) we'd like. |
Yeah, btw, the reason for the question in the first place is that I'm trying to create a project that has both AS and TS files, and I'm trying to figure out what's the best way to clearly separate them. |
What I've been doing so far is to have two source directories, both with their own tsconfig.json. For example |
I do the same - but I wanted to have a single TS file with loader code etc. per module. The way I decided to do this is by using
I'm closing this issue since I don't need it any more, and this is probably better addresses as a part of a bigger issue (e.g. #390). |
@dcodeIO Bump! Can we create support for optional extensions for full file names? |
I follow the discussion around the extension now a bit longer and I want to suggest a total rebrand from AssemblyScript to binode. |
Is it possible to change file extension for AssemblyScript source files to something other than
.ts
(e.g..as
)?I tried doing something like:
But getting the following error:
The text was updated successfully, but these errors were encountered: