Make phone provider a valid credentials provider

Currently if a user wants to sign in using account id and password that were created using phone provider the backend returns an error: "Uncaught Error: Provider phone is not a credentials provider", which I understand considering that there is initially no password set.
However one (like me :)) could implement a flow where
secret
(password) is set retrospectively and thus a phone provider could also be used for credentials, but perhaps only when
secret
field is actually populated.

Is something like that to be expected in the future?
Thanks.
Was this page helpful?