Forward Booking Questions in Query Parameters

[its-julian]

Is your proposal related to a problem?

It's frustrating that I'm not able to access the "booking questions" via query parameters on the confirmation page.

(Write your answer here.)

Describe the solution you'd like

Currently, Cal provides the option to "forward parameters" to the "Redirect on booking" page. However, the issue is that these parameters only include the basic event details.

There is no option/inclusion to forward the "booking questions" inside of the query parameters as well.

We need this data available on the booking page, so it would be great to have the option to forward these data points as well.

Describe alternatives you've considered

None, there's no way to solve this since Cal's infrastructure is controlling this entire step.

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.

[ciaranha]

@hariombalhara is there a way to do this? I think I recall you sharing a way before.

[hariombalhara]

It should be trivial to pass on booking responses in the query param.

Though we need to agree upon the naming convention as there are more query params apart from responses which could conflict with booking question identifiers

I think namespacing would be best for responses like responses.name

[Flash-Shivam]

@ciaranha @hariombalhara @its-julian I have implemeted this feature , kindly check the PR.

[anikdhabal]

Things to consider when fixing this issue:

1. You need to add a checkbox similar to the other parameter to include the booking response in the URL

2. If both checkboxes are checked, you will see two location parameters in the URL. This is because we provide the location parameter by default, and the location response is included in the booking response. So make sure the actual one location param should present.

3. As @hariombalhara suggested, namespacing would be best for responses like responses.name