Include semantics slices

[prabhu]

No description provided.

[gemini-code-assist]

Hello @prabhu, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request updates the version of the chen project from 2.3.4 to 2.3.5. This change affects the build.sbt, codemeta.json, meta.yaml, and pyproject.toml files. Additionally, it removes a dependency on org.benf % cfr from the jimple2cpg subproject and adds a filter for semantics.slices.json to the ConfigFileCreationPass in the jimple2cpg subproject. The removal of the decompiler and addition of the semantics slice filter suggests the inclusion of semantics slices functionality.

Highlights

• Version Update: The project version has been bumped from 2.3.4 to 2.3.5 across multiple configuration files.
• Dependency Removal: The cfr decompiler dependency has been removed from the jimple2cpg subproject.
• Semantics Slice Filter: A filter for semantics.slices.json has been added to the ConfigFileCreationPass in the jimple2cpg subproject, indicating the inclusion of semantics slices.

Changelog

Click here to see the changelog

• build.sbt
  • Updated project version from 2.3.4 to 2.3.5.
• codemeta.json
  • Updated project version from 2.3.4 to 2.3.5.
• meta.yaml
  • Updated project version from 2.3.4 to 2.3.5.
• platform/frontends/jimple2cpg/build.sbt
  • Removed dependency on org.benf % cfr.
• platform/frontends/jimple2cpg/src/main/scala/io/appthreat/jimple2cpg/passes/ConfigFileCreationPass.scala
  • Added filter for semantics.slices.json.
• platform/frontends/jimple2cpg/src/main/scala/io/appthreat/jimple2cpg/util/Decompiler.scala
  • Removed the Decompiler utility class.
• pyproject.toml
  • Updated project version from 2.3.4 to 2.3.5.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Did you know?

The .sbt build tool is based on Scala and allows for very flexible and expressive build definitions.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request updates the version number across multiple files and adds a new filter for semantics.slices.json. The changes seem straightforward and necessary for keeping the project consistent and up-to-date. However, I have a minor suggestion regarding the placement of the new filter in ConfigFileCreationPass.scala.

Summary of Findings

• ConfigFileCreationPass filter placement: Consider grouping custom filters together for better readability and maintainability in ConfigFileCreationPass.scala.

Merge Readiness

The pull request is almost ready for merging. The version updates are correct and the addition of the new filter seems functional. However, I recommend considering the placement of the new filter in ConfigFileCreationPass.scala for better code organization. Once this minor adjustment is made, the pull request should be good to go. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.