feat:tempalates functionality WIP

[nizzyabi]

What does this PR do?

This is the api call for templates feature we are building on the website. using a json file and connecting to some website code we allow users to copy pre filled templates so they can build routing forms, event types, and workflows quickly.

https://www.loom.com/share/73203081ba2849f69d81cd1916903786

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• run templates pr
• go to /templates in localhost:3001
• run this pr
• click on one of the templates and hit copy

• What is expected (happy path) to have (input and output)?
  you should be able to see a copied template

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "feat:tempalates functionality WIP". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cal-com-ui-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2025 0:27am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
cal	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 0:27am
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 0:27am

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (02/04/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add ready-for-e2e label" took an action on this PR • (02/07/25)

1 label was added to this PR based on Keith Williams's automation.

[github-actions]

E2E results are ready!

• Workflow #47001.1 latest results

[vercel]

You must have Developer access to commit code to cal on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes.

Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles

[PeerRich]

should this be in the core app? can we not host this in website or somewhere else?

[nizzyabi]

it’s calling the prisms schema that’s located in the web app. not sure if we can do that through the website. it was giving me errors on deployment when trying. do you have another approach in mind?

…

On Mon, Feb 10, 2025 at 7:31 AM Peer Richelsen ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ On apps/web/lib/templates/workflows.ts <#19096 (comment)>: should this be in the core app? can we not host this in website or somewhere else? — Reply to this email directly, view it on GitHub <#19096 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBP7RABVBWXN4IFY4OHIUUT2PCLYVAVCNFSM6AAAAABWO5IX22VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDMMBVGYYTSOBTGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>