Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
C#: Add VS Code model editor queries #14200
C#: Add VS Code model editor queries #14200
Changes from 1 commit
585fb9d
0cc74a2
e524e35
ff2cef3
8472b84
f468b2a
4693f72
93972a4
81a8eee
948e36a
489561f
dd79049
14a2b7f
eace7a4
044fb9f
3ebb9e1
45432f2
50a9219
13dd9a6
0fea21f
dc6def7
922ff7b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
All the callables are reported to be not supported as there doesn't exist any models for them.
Maybe consider to add some positive testcases for this as well.
It is possible to add a data extension file that only applies to an individual test case (
codeql test run
looks for.ext.yml
files with the same name as the test case). That is, if you add a file calledFetchFrameworkModeMethods.ext.yml
you can add models for some of your testmethods.This will implicitly help in testing that we got the predicates for
isSupported
right (e.g.getAnInput
andgetAnOutput
). The ApplicationMode testcase primarily targets "source" models.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.
Thanks for the suggestion! I've added 4 new methods with the 4 different types of models. The
summaryModel
andneutralModel
seem to work, but I can't get thesinkModel
orsourceModel
to work. Would you be able to take a look and check why those are not working?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.
I think the problem is that the implementation requires that for a callable to be identified as a source or sink there needs to be an actual call to it (this works fine for the queries that are just interested in callables NOT the source code). We need to do something else for the analysis that should respect source and sink models for EndPoints in the source code (I will look into this).