Skip to content
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

Fixes for empty tables #3844

Merged
merged 8 commits into from
Nov 21, 2024
Merged

Fixes for empty tables #3844

merged 8 commits into from
Nov 21, 2024

Conversation

madelondohmen
Copy link
Contributor

@madelondohmen madelondohmen commented Nov 18, 2024

Changes

  • Removes the bulk action button when the report history table is empty
  • Removes the empty findings table on the Crisis Room page and replace with an empty state text

The format of the code has changed, which might make the changed files hard to understand.
The only things I've added are if-statements around the tables to check if there's data

Issue link

Closes #3843

Demo

afbeelding

afbeelding

QA notes

  • Do a make reset
  • Check the crisis room --> Table shouldn't be visible, but instead you should see an empty state text
  • Check the report history page --> Bulk action button shoudn't be visible

Code Checklist

  • All the commits in this PR are properly PGP-signed and verified.
  • This PR only contains functionality relevant to the issue.
  • I have written unit tests for the changes or fixes I made.
  • I have checked the documentation and made changes where necessary.
  • I have performed a self-review of my code and refactored it to the best of my abilities.
  • Tickets have been created for newly discovered issues.
  • For any non-trivial functionality, I have added integration and/or end-to-end tests.
  • I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
  • I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.


Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

@madelondohmen madelondohmen self-assigned this Nov 18, 2024
@madelondohmen madelondohmen requested a review from a team as a code owner November 18, 2024 11:30
@ppvg
Copy link
Member

ppvg commented Nov 18, 2024

Are "findings" found? Or would something like "no findings have been made yet" make more sense?

@madelondohmen
Copy link
Contributor Author

Are "findings" found? Or would something like "no findings have been made yet" make more sense?

@ppvg This is the same text that we use in the Findings Report when there's no data.
@stephanie0x00 What do you think about this? If we want to change it, we should change it everywhere.

ammar92
ammar92 previously approved these changes Nov 19, 2024
@TwistMeister
Copy link
Contributor

Checklist for QA:

  • I have checked out this branch, and successfully ran a fresh make reset.
  • I confirmed that there are no unintended functional regressions in this branch:
    • I have managed to pass the onboarding flow
    • Objects and Findings are created properly
    • Tasks are created and completed properly
  • I confirmed that the PR's advertised feature or hotfix works as intended.
  • I checked the logs for errors and/or warnings and made issues where necessary

What works:

The 2 listed scenario's work

Bug or feature?:

  • The "Crisis room" across all organizations still shows 2 "empty" (count = 0) tables instead of text. Not sure if intended?
Screenshot 2024-11-19 at 14 31 22

@stephanie0x00
Copy link
Contributor

Are "findings" found? Or would something like "no findings have been made yet" make more sense?

@ppvg This is the same text that we use in the Findings Report when there's no data. @stephanie0x00 What do you think about this? If we want to change it, we should change it everywhere.

We should definitely update the text. It is quite complicated and nuanced though. For now we can update it to: "No findings have been identified yet.". We probably have to type out the nuances on the docs and make a reference to this page from the reports.

@underdarknl underdarknl merged commit e5dfc2b into main Nov 21, 2024
20 of 21 checks passed
@underdarknl underdarknl deleted the feature/fixes-for-empty-tables branch November 21, 2024 13:38
Copy link

sonarcloud bot commented Nov 21, 2024

jpbruinsslot added a commit that referenced this pull request Nov 27, 2024
* main: (60 commits)
  Increase max number of PostgreSQL connections (#3889)
  Fix for task id as valid UUID (#3744)
  Add `auto_calculate_deadline` attribute to Scheduler (#3869)
  Ignore specific url parameters when following location headers (#3856)
  Let mailserver inherit l1 (#3704)
  Change plugins enabling in report flow to checkboxes (#3747)
  Fix rocky katalogus tests and delete unused fixtures (#3884)
  Enable/disable scheduled reports (#3871)
  optimize locking in katalogus.py, reuse available data (#3752)
  Updates boefje clearances and descriptions (#3863)
  Fixes for empty tables (#3844)
  Fix cron for last day of the month (#3831)
  Sub reports for Aggregate Report (#3852)
  Add start time to scheduled reports (#3809)
  Add configuration setting for number of octopoes workers (#3796)
  Limit requesting prior tasks for ranking in scheduler (#3836)
  Let local plugins (files) take precedence over database entries (#3858)
  Skip empty queues in the Rocky worker (#3860)
  Report types listed in a modal @ report plugins (#3718)
  Support a Schedule without a schedule in scheduler (#3834)
  ...
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.

Bulk actions visible when report history is empty
6 participants