Hey there @hmnd!

We typically don't expose listeners/handlers for properties that we don't adjust internally, meaning the visibleMonths prop is read-only from Bits UI's perspective. The developer passes that prop and can control it in userland, meaning they can hook into their specific implementation.

To determine what months are visible, you can use a combination of the placeholder and visibleMonths to determine that.

Hey @huntabyte, thanks for taking a look at this.

As far as I'm aware, visibleMonths isn't currently exposed or controllable from userland. Because of that, I followed the implementation of onStartValueChange instead, internally exposing months to the svelte components to achieve that. Placeholder is also not terribly helpful, as it doesn't provide the end date in range calendars and doesn't provide the actual visible range (although this can technically by calculated by the developer, but that feels like unnecessary doubling of effort).

Thus I think either a handler like I've implemented or a read-only binding to months or visibleMonths is necessary.

Ah, I see what you mean. I was thinking of numberOfMonths instead of visualMonths. Let me review this and think on it a little bit!

Happy to discuss/provide feedback in chat on discord if preferred too - @.hmnd on there :)

Thanks!