When using the “Forwarded email alias” feature in Bitwarden, the app doesn’t allow you to specify custom alias text for a standard alias. A lot of people like to name their aliases as such “amazon{at}username.anonaddy” but with this feature missing in Bitwarden, you can only generate a random string, e.g. “sbsdghb{at}username.anonaddy” forcing users who want the custom font to go to AnonAddy and create the email first, then come back to Bitwarden to use it.
The AnonAddy API (and I’m sure the other providers) have the ability to pass the “custom” format type to alias generation along with “local_part” for the text.
I see in the Bitwarden source code only the “domain” and “description” fields are being used in the API. It should be pretty arbitrary to add the API fields for format to custom and local_part field to whatever the user enters in Bitwarden instead of making the “Generator” input uneditable.
Could this be added to the roadmap?