You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a significant notion, and one I've probably mentioned before in more issues.
I've been thinking of using match fields like url for parts of the schema that take a url of a form, like password reset tokens. This would use the same matching syntax as Chrome Extension manifests and Greasemonkey @match rules, where it's basically just globbing.
I'm pretty sure that'd be sufficient for any practical use case, but there's also a case that could be made for tighter RegExp-based rules, or rules describing the formats of tokens that get inserted into the URL, or lots of things like that; for now, I think that's best to just not specify at that level of detail, but room should be left for it.
The text was updated successfully, but these errors were encountered:
This is a significant notion, and one I've probably mentioned before in more issues.
I've been thinking of using
match
fields likeurl
for parts of the schema that take a url of a form, like password reset tokens. This would use the same matching syntax as Chrome Extension manifests and Greasemonkey@match
rules, where it's basically just globbing.I'm pretty sure that'd be sufficient for any practical use case, but there's also a case that could be made for tighter RegExp-based rules, or rules describing the formats of tokens that get inserted into the URL, or lots of things like that; for now, I think that's best to just not specify at that level of detail, but room should be left for it.
The text was updated successfully, but these errors were encountered: