You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: Pass name and email attribute to calnode-booking component #255
I've searched existing issues and this isn't a duplicate.
This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.
What's the bug?
This is a feature, not a bug.
It would be great to pass name and email attribute to calnode-booking component so the booking form has already these fields filled and locked.
This is very helpful if for example the logged in user want to book a slot.
One thing worth settling before it gets built, because it changes the shape of the work: "filled and locked" is a user-experience affordance, not a guarantee. The form is client-side, and POST /v1/bookings still accepts whatever name and email a request carries — anyone can submit different values with curl. So an attribute that renders the inputs read-only makes the good path smoother, but it does not prove the booking came from that person.
Which of these do you actually need?
Convenience — the embed sits on a page where the customer is already known, and you want them to not retype it. Read-only inputs are fine here, and this is what your example describes.
Proof of identity — "this booking really was made by John". That needs something the browser cannot forge, e.g. your backend signs a short-lived token that Calnode verifies server-side. Bigger job, and it would need a decision about what the signature covers.
If it's (1), this is a small, self-contained change and I'd take it. If it's (2), say so and I'll write it up properly instead of shipping something that looks like a lock but isn't.
No timeline committed either way — tracking it here is enough for now.
Activity
pullfrog commentedon Nov 14, 2026
shockalotti commentedon Nov 17, 2026
Thanks — this is a sensible ask, and you're right that it isn't a bug. I've relabelled it
enhancement(it came in through the bug template).It's cheap to build.
embed.jsconstructs the booking form itself, so this is reading two attributes and pre-filling the inputs:One thing worth settling before it gets built, because it changes the shape of the work: "filled and locked" is a user-experience affordance, not a guarantee. The form is client-side, and
POST /v1/bookingsstill accepts whatever name and email a request carries — anyone can submit different values with curl. So an attribute that renders the inputs read-only makes the good path smoother, but it does not prove the booking came from that person.Which of these do you actually need?
If it's (1), this is a small, self-contained change and I'd take it. If it's (2), say so and I'll write it up properly instead of shipping something that looks like a lock but isn't.
No timeline committed either way — tracking it here is enough for now.
davidmunoz-dev commentedon Nov 17, 2026
Yes sorry I couldn't find the feature template.
Thanks for the quick reply. For now only the convenience case would fit my needs.