Skip to content

Feature request: Pass name and email attribute to calnode-booking component #255

Open

Description

@davidmunoz-dev

Before submitting

  • 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.

Steps to reproduce

<calnode-booking slug="slug" name="John Doe" email="john@doe.com"></calnode-booking>

Calnode version / commit

0.14

How are you running Calnode?

Self-hosted — Docker

Logs, screenshots, or anything else

No response

Activity

  1. pullfrog commented on Nov 14, 2026

    @pullfrog
    Contributor
  2. shockalotti commented on Nov 17, 2026

    @shockalotti
    Contributor

    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.js constructs the booking form itself, so this is reading two attributes and pre-filling the inputs:

    <calnode-booking slug="slug" name="John Doe" email="john@doe.com"></calnode-booking>

    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?

    1. 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.
    2. 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.

  3. added
    enhancementNew feature or request
    and removed
    bugSomething isn't working
    on Nov 17, 2026
  4. davidmunoz-dev commented on Nov 17, 2026

    @davidmunoz-dev
    Author

    Yes sorry I couldn't find the feature template.
    Thanks for the quick reply. For now only the convenience case would fit my needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions