Skip to content

Conversation

@luisamaralh
Copy link

The first implementation of the module to collect sensitive APIs from invoked methods


}
return name;
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need these functions to implement the feature of mining calls to sensitive APIs? Perhaps you have implemented them just to familiarize yourselves with the architecture / and the Rascal language. If this is the case, I would recommend removing these methods.

};

return "";
} No newline at end of file
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should discuss again this implementation. IMO, we should simplify the interface of the sensitiveFind function. Actually, even the name is not really good. It should receive two arguments: a list of strings with the signature of sensitive methods and an ExecutionContext. Only in this way I could use this implementation in a pipeline with a set of analyzes. This is a bit tough to explain here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants