Repository navigation
Replies: 1 comment 1 reply
|
Thanks — I understand the use case (available 9-5, but only want to take ~2h of bookings a day for the side business). Honest answer on why this is not a small toggle: the slot engine is currently stateless per start time (rules + busy intervals in, slots out). A daily cap needs day-level accounting — count what is already booked that day, then suppress the rest once the budget is hit. Doable, but it is a new limiter with real design questions, not a setting I want to guess wrong on:
Tracking as #91. If you can add a line on your answers to the three questions above, it directly shapes whatever gets built. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Say I have a side business, limited to a specific amount of time per day, I would really like to have the option of an added availability limit. Say I set it to max 2h / day, calnode would accept events up to this amount of length. Like I am available 9-5 but only for 2h a day.
Would that be possible please?
All reactions