Italo
I would agree that Lazy Objects support would be great, especially for services that require a huge set up when instanced. The main problem I have with Lazy objects is...
> @DarkGhostHunter could you explain where the claim that "The main problem I have with Lazy objects is testing" comes from? :D I don’t see any issue with testing -...
AFAIK they cannot. One of the reasons why Google got away from using JAVA for Android, but compiling to something else. Also, would make MeiliSearch and TypeSense unviable.
Any update on this?
I understand. I believe the important part is the backend. Without it the developers will have to create their own logic, which may be a deal breaker.
I'll add it to version 2.0. Just to note: 1. Sends WebAuthn Recovery Email using a trait (much like `SendsRecoveryEmail`). 2. WebAuthn Recovery form (where the recovery sends the user...
> I think this method of recovery will add a weak security, normaly you should have two devices register with WebAuthn in case you loose access to the first one....
> if such a way of recovery exists it is possible to bypass webauthn entirely which makes it like another password. (some email providers don't even support any 2fa) >...
Not in Ethel foreseeable future. Also, I'm not looking forward to it since I can't think of a feature that I would want to add and would be breaking enough...
Oh, I will release v2 as pre-release right now because I just figured Laravel 11 is coming soon. Also, goodbye PHP 8.0