Skip to content

Differentiate Typescript of Javascript #1585

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
manumafe98 opened this issue Apr 3, 2025 · 1 comment
Open

Differentiate Typescript of Javascript #1585

manumafe98 opened this issue Apr 3, 2025 · 1 comment

Comments

@manumafe98
Copy link

Would it not make sense to add concepts on the typescript track to instruct the differences between typescript and javascript.
For example:

  • Introduction to types (and how to create them)
  • Introduction to interfaces
  • Interfaces vs types and when to use them
  • Utility types
  • Introduction to Generics

We could use the main and core concepts of javascript and use them here as well and start from there to create this little differentiations.
Let me think what your thoughts are of this one, and also I'm glad to help on the creation of all this if you guys need a hand.

@SleeplessByte
Copy link
Member

Yes, this is the plan, but with the I/O starvation of the test runner, development on this has been halted for a little while. You can see I made a start here: exercism/typescript-test-runner#73

  • If we can get rid of Copying x to y steps, the test runner can be made fast again. So we can continue work. For this, we likely will need to move away from jest as jest will not work correctly if you try to run it "out of tree". Eg if jest is in folder A and the content is in folder B and B is not a sub-path of A, jest will not work as expected.
  • In the next few months we'll also implement a in-web version of the track to make feedback lightning fast (go try it out, you can also try out javascript).

Once both are in place, proper concept exercises can be made for the TS track, which has been long planned. Starting before this is in place will have a very high chance of required rework as I do not yet know what the track infrastructure will look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants