JS: Recognize Express param value callback as RemoteFlowSource#3424
Conversation
esbena
left a comment
There was a problem hiding this comment.
Nice spot. I am curious about how common this is.
Have you considered adjusting
(also: change-note)
|
Thanks for pointing that out. Turns out we even misclassified the request and response parameters of these route handlers, due to them taking 4 parameters. Updating this was more tricky than it had any right to be. PTAL. Evaluation looks a bit swingy, will re-run the slowest. |
esbena
left a comment
There was a problem hiding this comment.
Updating this was more tricky than it had any right to be
You don't say! :(
The implementation looks good though.
JS: Go back to disjunction 8fcd024
Is this due to an optimizer limitation?
I suppose we also need a change-note for - [express](https://www.npmjs.com/package/express)
No, just formatting. |
|
Re-run of slowest is nowhere near as bad as in the original evaluation, but still a bit biased. I'll look at some tuple counts to see what's going. |
…hared.qll Co-authored-by: Esben Sparre Andreasen <esbena@github.com>
9f68e3f to
d84f1b4
Compare
|
The use of As a bonus, we now recognize Hopefully that's the last feature-creep in this PR. |
esbena
left a comment
There was a problem hiding this comment.
Excellent. Thanks for creeping so fast :)
|
Security/nightly looks good. |
A
paramroute handler in Express takes the value of the parameter in the 4th argument as seen here. This PR adds it as aRequestInputSource.