-
Notifications
You must be signed in to change notification settings - Fork 500
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
Ts node support + tests #248
Conversation
I have two concerns:
|
Oh, regarding my second point, I've just seen that the environment variable is actually set: https://github.com/SAP-samples/cloud-cap-samples/pull/248/files#diff-2d29ae20792820e80f8924914e7010e5e25076584cff77b50001f7353d7860a9R1 afterAll(() => {
delete process.env.CDS_TYPESCRIPT;
}); Or remember which was the original value before assigning it |
The preset says quite explicitly:
So I would expect it to do exactly the same as before (but including tsx for transformation). |
Yes, that's also my assumption. If it doesn't harm or slow down the js tests too much, then fine with me. |
Done |
Otherwise, the question is whether there should be a separate sample repository for TypeScript (as it would need to contain ts-config and maybe other configurations in the long run) to separate the necessary configurations of JavaScript and TypeScript for newcomers. It will be hard to distinguish what is not to compromise the JS parts and what is (really) necessary if I go the TS way. Deleting the variables afterward, for example, shouldn't be required if I decide to go complete TypeScript, right? Therefore, it could not be obvious. Since the environment variable is not even described in capire or the changelog, it's a bit of a search for users who want to test the TypeScript files anyways. |
@Kkoile we seem to have issues w/ your CLA. Can you check? Could be that you used a wrong email address not connected to your current GH account. |
That's a constant trade-off in how many repos to cut the samples, given that there is maintenance overhead of each new one. That was the reason for the current mono-repo.
It is (with the wrong value though, about to fix this). |
@Kkoile I have rewritten your commits with my email address if you don't mind. This way, we get over the CLA barrier. |
This allows TS specifics to stay local in just one package
All TS related stuff is now isolated in the |
Sorry, I'm always a bit behind timewise with my private github account. But sinced you merge the pull request, I guess everything is clear now and there's nothing more to do? |
Right, all is settled :) |
@chgeo With the documentation saying "We invite you to contribute and help us complete the typings as appropriate. Sounds interesting? Reach out to us." -> Whom would we need to reach out to? |
@tsteckenborn you can reach out to me (christian.georgi@sap.com) and maybe nils.hirsekorn@sap.com (@Kkoile), who is an active TS user here at SAP. (@iwonahahn FYI) |
No description provided.