9 Commits

Author	SHA1	Message	Date
yoff	1a57f81aca	Merge pull request #12537 from yoff/python/captured-variables-for-typetracking ... Python: Captured variables for type tracking and the API graph	2023-05-09 12:34:22 +02:00
Mathias Vorreiter Pedersen	e650df810d	Python: Accept consistency changes.	2023-05-03 20:33:00 +01:00
Rasmus Lerchedahl Petersen	2318752c14	python: add reads of captured variables to ... type tracking and the API graph. - In `TypeTrackerSpecific.qll` we add a jump step - to every scope entry definition - from the value of any defining `DefinitionNode` (In our example, the definition is the class name, `Users`, while the assigned value is the class definition, and it is the latter which receives flow in this case.) - In `LocalSources.qll` we allow scope entry definitions as local sources. - This feels natural enough, as they are a local source for the value, they represent. It is perhaps a bit funne to see an Ssa variable here, rather than a control flow node. - This is necessary in order for type tracking to see the local flow from the scope entry definition. - In `ApiGraphs.qll` we no longer restrict the result of `trackUseNode` to be an `ExprNode`. To keep the positive formulation, we do not prohibit module variable nodes. Instead we restrict to the new `LocalSourceNodeNotModule` which avoids those cases.	2023-03-16 12:55:58 +01:00
Tom Hvitved	404ead8a18	Python: Update expected test output	2023-03-16 08:40:53 +01:00
Tom Hvitved	39fea378b8	Python: Update expected test output	2022-12-13 09:53:01 +01:00
Tom Hvitved	8f701cf1cb	Python: Update expected test output	2022-12-05 14:33:06 +01:00
Rasmus Wriedt Larsen	88f703af1f	DataFlow: Accept changes to .expected	2022-11-10 22:13:34 +01:00
Tom Hvitved	f4b82cb2e8	Python: Update expected test output	2022-09-22 15:01:40 +02:00
Erik Krogh Kristensen	095c73f1fe	redo the ApiGraph testing framework	2022-02-03 23:10:38 +01:00