-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement default range for Range Picker #65
Conversation
Hello @antony, curious is Beyonk still maintaining this repository? If so, I could help out with a few more PR's to address existing issues. Let me know! |
Hi Timothy,
Yes we are indeed :) PRs are welcome!
Thank you,
Antony
On Mon, 10 Apr 2023 at 04:24, Timothy Wheelock ***@***.***> wrote:
Hello @antony <https://github.com/antony>, curious is Beyonk still
maintaining this repository? If so, I could help out with a few more PR's
to address existing issues. Let me know!
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABVORLDOSVBWDB2XEB4YZ3XAN4OPANCNFSM6AAAAAAWSFN7HE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
…________________________________
ꜽ . antony jones . http://www.enzy.org
|
Awesome, glad to hear it. From my searching this looks like one of the best datepickers out there right now for Svelte. As far as contributing, this PR is a start! |
Looks great. Thank you for this. I'll review and merge later today! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just switching to meet our linting rules
This is merged now, but docs fail, and I'm not sure why. I notice they are still on snowpack, so we probably should move this lib to SvelteKit. I won't have time immediately, but will get to it ASAP. |
Hello.
Thanks for your work on this library, it is one of the best datepickers out there for Svelte right now. However, in my use, I ran into a significant issue where the default date range for range picker is hard-coded to 1 month, rather than being configurable.
This PR exposes the default range as input props, so that this can be configurable.
This also solves issue #43
Usage: