Skip to content

Frontend - Analyzables page #2865

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

Open
wants to merge 7 commits into
base: frontend_analyzables
Choose a base branch
from

Conversation

carellamartina
Copy link
Contributor

Description

  • created a new page for analyzables search

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

  • I have read and understood the rules about how to Contribute to this project
  • The pull request is for the branch develop
  • A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
    • I strictly followed the documentation "How to create a Plugin"
    • Usage file was updated. A link to the PR to the docs repo has been added as a comment here.
    • Advanced-Usage was updated (in case the plugin provides additional optional configuration). A link to the PR to the docs repo has been added as a comment here.
    • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration. ("How to share a plugin with the community")
    • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip and you added the default tests for that mimetype in test_classes.py.
    • If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook by following this guide.
    • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
    • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
    • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information. This is required for Health Checks.
    • If the plugin requires mocked testing, _monkeypatch() was used in its class to apply the necessary decorators.
    • I have added that raw JSON sample to the MockUpResponse of the _monkeypatch() method. This serves us to provide a valid sample for testing.
  • I have inserted the copyright banner at the start of the file: # This file is a part of IntelOwl https://github.com/intelowlproject/IntelOwl # See the file 'LICENSE' for copying permission.
  • If external libraries/packages with restrictive licenses were used, they were added in the Legal Notice section.
  • Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors.
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.
  • After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review by using GitHub's reviewing system detailed here.

@carellamartina
Copy link
Contributor Author

Schermata del 2025-05-14 14-15-00

@carellamartina carellamartina requested a review from drosetti May 15, 2025 09:54
@drosetti
Copy link
Contributor

I suggest to change the target branch. Create another branch from develop and merge analyzables_page into this new branch. In this way we will merge everything in the develop branch once all the feature is completed

@carellamartina carellamartina changed the title Frontend - Analyzables page + User reports Frontend - Analyzables page May 15, 2025
@carellamartina carellamartina changed the base branch from develop to frontend_analyzables May 15, 2025 10:16
@carellamartina carellamartina marked this pull request as ready for review May 15, 2025 10:17
Copy link
Contributor

@drosetti drosetti left a comment

Choose a reason for hiding this comment

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

I suggest to swtch in the navbar the "dashboard" with "analyzables" in this way the dashboard is the first one from the left.


def get_queryset(self):
user = self.request.user
return super().get_queryset().visible_for_user(user)

@action(detail=False, methods=["post"])
Copy link
Contributor

Choose a reason for hiding this comment

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

why a post insted of a get?

Comment on lines +33 to +60
def test_list(self):
self.client.force_authenticate(user=self.user)
response = self.client.get(self.URL)
self.assertEqual(response.status_code, 200, response.content)
result = response.json()
self.assertIn("count", result)
self.assertEqual(result["count"], 1)

def test_get_analyzables(self):
self.client.force_authenticate(user=self.user)
response = self.client.post(
f"{self.URL}/get_analyzables",
data=["test.com"],
format="json",
)
self.assertEqual(response.status_code, 200, response.content)
result = response.json()
self.assertEqual(result[0]["id"], self.an.pk)

self.client.force_authenticate(user=self.user)
response = self.client.post(
f"{self.URL}/get_analyzables",
data=["noanalyzable.com"],
format="json",
)
self.assertEqual(response.status_code, 200, response.content)
result = response.json()
self.assertEqual(result[0]["tags"], ["not_found"])
Copy link
Contributor

Choose a reason for hiding this comment

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

list and get_analyzables seems very similar, we need a custom API ? We cannot just call the list ?

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.

2 participants