We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I understand that this is just a matter of aesthetics here and my request is not very important, but there are some scenarios named:
access_web_archive.closed access_web_archive.intranet access_web_archive.listmaster access_web_archive.owner access_web_archive.private access_web_archive.public
while others are named using a different pattern:
archive_mail_access.closed archive_mail_access.default archive_mail_access.owner archive_mail_access.private archive_mail_access.public
Only one pattern would be desirable, either archive_mail_access.* and archive_web_access.* , or access_web_archive.* and access_mail_archive.*
Thank you very much. Regards.
The text was updated successfully, but these errors were encountered:
@qosobrin, I agree to consistent naming. Please go on.
Sorry, something went wrong.
Merge pull request #227 from ikedas/pr-217
f2774e2
Issue #216: Unify scenario names #217 by qosobrin
@qosobrin, your PR was merged. Thanks for good change!
Sorry for the delay. I was out for a while. Thank you for the merge.
No branches or pull requests
I understand that this is just a matter of aesthetics here and my request is not very important, but there are some scenarios named:
while others are named using a different pattern:
Only one pattern would be desirable, either archive_mail_access.* and archive_web_access.* , or access_web_archive.* and access_mail_archive.*
Thank you very much.
Regards.
The text was updated successfully, but these errors were encountered: