Skip to content

python: remove library annotation to clean up QL warnings. #7788

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

Merged
merged 2 commits into from
Feb 2, 2022

Conversation

yoff
Copy link
Contributor

@yoff yoff commented Jan 31, 2022

Should put these functions in a private module instead, as indicated by the documentation for library?

to clean up QL warnings.
Should put these in a private module instead?
@yoff yoff requested a review from a team as a code owner January 31, 2022 07:51
@RasmusWL
Copy link
Member

Maybe this should be obvious, but what warnings are we getting for these? (and why?)

@tausbn
Copy link
Contributor

tausbn commented Jan 31, 2022

Maybe this should be obvious, but what warnings are we getting for these? (and why?)

There's a QL-for-QL query that checks for this presence of this annotation. The annotation itself is deprecated (though not to the degree that it actually emits a compiler warning).

@yoff yoff changed the title python: remove library annotation to clean up QL warnings. Should put these in a private module instead? python: remove library annotation to clean up QL warnings. Jan 31, 2022
@yoff
Copy link
Contributor Author

yoff commented Jan 31, 2022

I made it also remove the auto-generated annotations. There is a PR to not auto-generate those.

Copy link
Contributor

@tausbn tausbn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. We might want to also fix up the QLDoc to get rid of those warnings.

@codeql-ci codeql-ci merged commit 7bb11b8 into github:main Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants