-
Notifications
You must be signed in to change notification settings - Fork 97
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
Enhance TypeScript documentation regarding deployment #710
Comments
Hi Gregor, thank you for pointing this out. I'll be working on this and let you know when this is done. Thanks, |
Hi Gregor, half a year ago, @sebastianesch provided the MTA deployment part: https://cap.cloud.sap/docs/tools/cds-typer#integrate-into-your-multitarget-application When discussing and researching, the question on the use case arose with our colleagues. Having that compile step added to the deployment means that you want to use It's especially interesting because we have an explicit note in our docs that states to not use Looking forward to your thoughts on that. All the best, |
Hi René, I don't want to use In the archived btp-full-stack-typescript-app example it's done in mta.yaml#L16 with
Beside this also the tsconfig.json must be provided. Hope that clarifies my request. Best Regards |
Hi Gregor, thank you for bringing this discrepancy to our attention! Best, |
Hello CAP Documentation Team,
looking at the documentation page Using TypeScript the part for local development is nicely covered. But when I use
cds add mta
I don't see the needed compile step being added. Unfortunately the sample repository:https://github.com/SAP-archive/btp-full-stack-typescript-app
was archived and the branch:
https://github.com/SAP-samples/cap-sflight/tree/typescript
seems not being updated either. I would suggest to add the deployment best practice for CAP TypeScript directly in the documentation.
Best Regards
Gregor
The text was updated successfully, but these errors were encountered: