Wildcard implementation in website property of Login Item

bedilbek

website property inside 1Password Login Item is a great feature which helps to automatically detect and auto fill username and password into the form fields. What's great about it and what's already implemented:

1. You can actually create multiple website properties and still any of the matching websites will work
2. You can set the domain to the website property and any subdomain of that domain will work
3. You can set the domain to the website property and any subdirectory of that domain will work

However I can give an example from netlify (web deployment platform) which won't match with any of the above 3 features. Let's assume I am developing web application and I set my application url as https://some-app.netlify.app. Netlify has a greate feature to customize subdomains based on the different deployment strategies. For example if I am now working on new github branch and I create a PR #100, then Netlify automatically creates new deployment url https://deploy-preview-129--some-app.netlify.app which is not just a subdomain of netlify.app because there can be thousands of app in netlify, however this is slightly different customized subdomain of netlify with some predefined prefix.

So what I would I like is implementation of some custom wildcard options for the subdomains like *sub.domain.com where I can have potentially anything in the place of wildcard *.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Dave_1P

Hello @bedilbek! 👋

Thank you for the detailed explanation! I can definitely see how wildcards for autofill behaviour rules would be useful in the case of Netlify and, while I can't make any promises, I've filed a feature request to have our product team look into this further.

I appreciate you taking the time to send in your feedback. 🙂

-Dave

ref: PB-44282690