Rasmus Wriedt Larsen 00ea0cebc3 Python: More Flask modeling kinda works ...

It "kinda" works now, but it really is not a pretty solution. Adding all these
"tracked" objects is SUPER annoying... it _would_ be possible to skip them, but
that seems like it will give the wrong edges for dataflow/taintflow queries :|

A good chunk of it should be able to be removed with access-paths like C# does
for library modeling. Some of it could be solved by better type-tracking API
like API Graphs... but it seems like we generally are just lacking the
nice-to-have features like `.getAMemberCall` and the like. See
https://github.com/github/codeql/pull/4082/files#diff-9aa94c4d713ef9d8da73918ff53db774L33

2020-09-22 16:28:25 +02:00

..

flask

Python: More Flask modeling kinda works

2020-09-22 16:28:25 +02:00