-
Notifications
You must be signed in to change notification settings - Fork 10
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
arePasskeysSupported #23
Comments
Looking through the code, i see a number of the capabilities in the default Passlock class, that are not present in the Passlock class in Sveltekit/superforms (i am using sveltekit) , The Passlock class in superforms should be an extension of the base Passlock class so that those capabilities are available to sveltekit users as it is to others . |
I had it like this in my project and was able to access and use the base Passlock class methods
i removed the private readonly passlock property , extended the base Passlock class and called super in the constructor |
@thobson ^^ |
Thanks for your messagesI will reply in full at the weekend (working on my day job now!) but in summary yeah I need to expose the same functionality via the SvelteKit adapter as I do in the regular class. I’m actually going to shake things up a bit and see close functions vs classes as it’s better for tree shaking. (I think?)If you have any other suggestions as to how to improve the DX please let me know. I’m always keen to learn from anyone using the library.
|
Additionally, in my login schema , i added a field isEmailVerified , and made this slight change in the onSubmit method of Seveltekit-superforms as well as populating that field once a prinicpal is retrieved using emailVerified field , back in onSubmit , i can decide to call resendEmail and redirect the user to the email verification code and link . with all of this, it seems like the sveltekit-superforms bit should be in user land or should be made maleable with config .
and in the login call
|
@shiftlabs1 can I ask you to create a separate issue for your use case? If I’ve understood you correctly you want the ability to verify a users email not just during the initial registration but also during login? BTW I'm going to expand the server side API and include a |
@joshua1 For now, I've exposed |
Sorry @thobson . Both accounts happened to be mine (Shiftlabs1 and joshua1) . The sendVerificationEmail will be helpful. Thanks |
I see this in the docs to check if passkeys are supported in a browser but cant seem to find the right path to import it from. did something change ? I also tried isPassKeySupport but cant import it too. What is the right call to perform this check ?
The text was updated successfully, but these errors were encountered: