Skip to content
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

feat: v2 routing forms responses endpoints #19319

Conversation

supalarry
Copy link
Contributor

Linear CAL-5170

Copy link

linear bot commented Feb 17, 2025

@keithwillcode keithwillcode added core area: core, team members only platform Anything related to our platform plan labels Feb 17, 2025
Copy link

vercel bot commented Feb 17, 2025

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

Name Status Preview Comments Updated (UTC)
cal-com-ui-playground ❌ Failed (Inspect) Feb 21, 2025 7:22am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Visit Preview Feb 21, 2025 7:22am
calcom-web-canary ⬜️ Ignored (Inspect) Visit Preview Feb 21, 2025 7:22am

This reverts commit b641c06.
@supalarry supalarry marked this pull request as ready for review February 18, 2025 15:03
@supalarry supalarry requested a review from a team as a code owner February 18, 2025 15:03
@graphite-app graphite-app bot requested a review from a team February 18, 2025 15:04
@dosubot dosubot bot added the routing-forms area: routing forms, routing, forms label Feb 18, 2025
Copy link

graphite-app bot commented Feb 18, 2025

Graphite Automations

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

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

Copy link
Contributor

github-actions bot commented Feb 18, 2025

E2E results are ready!

@supalarry supalarry changed the title feat: v2 routing forms endpoints feat: v2 routing forms responses endpoints Feb 18, 2025

async getRoutingFormResponses(routingFormId: string) {
const responses = await this.routingFormsRepository.getRoutingFormResponses(routingFormId);
return this.routingFormsResponsesOutputService.getRoutingFormResponses(responses);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: They both have same name and very different purpose.
One fetches from DB and later parses it. Maybe we can call the later one, parseRoutingFormResponses or buildRoutingFormResponses

@hariombalhara
Copy link
Member

hariombalhara commented Feb 20, 2025

Codewise LGTM!! Don't have V2 setup locally so, didn't test it.

Also, completely new endpoints and controllers so safe to go in general too.

@supalarry supalarry enabled auto-merge (squash) February 20, 2025 11:34
@supalarry supalarry merged commit e6daed7 into main Feb 21, 2025
39 checks passed
@supalarry supalarry deleted the lauris/cal-5170-platform-feat-get-organizations-routing-forms-responses branch February 21, 2025 08:08
MuhammadAimanSulaiman pushed a commit to hit-pay/cal.com that referenced this pull request Feb 25, 2025
* wip: routing forms responses

* refactor structure

* Revert "refactor structure"

This reverts commit b641c06.

* routing forms

* remove unused file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core area: core, team members only platform Anything related to our platform plan ready-for-e2e routing-forms area: routing forms, routing, forms
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants