-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Python: ObjectAPI to ValueAPI: ExpectedMappingForFormatString #2827
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
Python: ObjectAPI to ValueAPI: ExpectedMappingForFormatString #2827
Conversation
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.
Looks good. The query could do with some autoformatting, but otherwise everything looks OK to me.
I think we'll need to revisit isSequence
at some point, as what we have right now doesn't account for sets, but that doesn't have to be in this PR.
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.
One small comment, otherwise ready to merge!
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.
Sorry to disrupt this PR, but I think we need to agree on how we want to handle referencing things by name.
I've seen this use of someClass.getName() = "FooBar"
in multiple places. Should we be using someClass = Value::named("FooBar")
instead? I've been doing that on my own, but I think we need a clear guideline on that in general for Python 🐍 @Semmle/python
I've made a suggestion for an instance I found in this PR, but please wait with accepting it before we have consensus 😛
Co-Authored-By: Rasmus Wriedt Larsen <rasmuswriedtlarsen@gmail.com>
…f github.com:BekaValentine/ql into objectapi-to-valueapi-expectedmappingforformatstring
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.
Yep, I think it's good now 👍
This PR is part of the effort to modernize the Expressions queries, moving away from the use of
refersTo
and associated APIs, and towardspointsTo
and its associated APIs.