-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Ability to bind date
object
#145
Comments
This is weird, because setting value to The error from your log is probably referring to this line: (stringValue || '').split(',') but as you can see, |
@bluepuma77 Are you sure you are binding string as a value? |
@mskocik Sorry, it's a big setup, so reproduction would take some time. Today I got a slightly different error:
which points to this line:
I think I might bind a Date instead of a String. And when I turn it into a String, then SuperForms using its schema indicates the field as error... |
yes, passing the Date would explain given error. String is expected, Date objects are used internally. But they are exported on |
@mskocik Would the current architecture allow for an extension like
to enable a date variable to be passed in and out? |
I would need to try it out, but I think it might be possible but I wouldn't recommend it due possible issues across timezones |
@bluepuma77 Is this still relevant for you? |
For now I switched to date-picker-svelte because that uses Date and therefore works better with SuperForms. |
Sure, no problem. Btw to you know, you could use proxy for that? |
date
object
Trying to get svelty-picker to work with sveltekit-superforms and my own form input builder.
My current issue is that after submit and reload, svelty-picker breaks, I assume because the
bind:value
isnull
orundefined
.Is it possible to improve this, so even if
null
orundefined
is supplied, the date is shown empty and not breaking the component? Maybe some more checking or usingtry catch
?The text was updated successfully, but these errors were encountered: