-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Python/JS: Make most of the new library private #6200
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
Conversation
|
Much more can be made private. |
Do you mean in other files or in the new file? I felt I could not hide previously exposed stuff in the javascript codebase, and I want the python files to be identical. |
|
Ah, I guess I could make most classes private also.. |
|
Oh, and I missed all the typed predicates 🤦 |
This mirrors `SuperlinearBacktracking.qll` An alternative is to keep it private and import it again in the query files.
RasmusWL
left a comment
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.
👍 from the Python side
The library is less new for JavaScript (~4-6 months?). Is this privatization a breaking change for JavaScript? Or did we already cross that bridge when the shared RegExp libraries for Python/JavaScript were introduced? |
I believe this code was recently hidden in a |
That is correct, it was inside |
esbena
left a comment
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.
In that case: 👍 from JS
A new library was recently introduced. As much as possible of that should be made private.