-
Notifications
You must be signed in to change notification settings - Fork 7
Added a BannedNamespace IssueKind. #32
New issue
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
base: main
Are you sure you want to change the base?
Added a BannedNamespace IssueKind. #32
Conversation
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Tushar Mukherjee <t***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce Inc. Contributor License Agreement and this Pull Request will be revalidated. |
@@ -212,6 +212,22 @@ pub(crate) fn analyze( | |||
); | |||
} | |||
|
|||
if let Some(banned_message) = function_storage.banned_namespace_message { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also not sure if this is correct.
Description:
Added a new
IssueKind
called BannedNamespace for scenarios where we want to ban the usage of functions under a given namespace.