Skip to content

fix: missing implementation groups on exports #1851

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

Merged
merged 7 commits into from
Jun 13, 2025

Conversation

Axxiar
Copy link
Contributor

@Axxiar Axxiar commented Apr 14, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Improved display logic for implementation groups in compliance assessments, showing the section only when relevant groups are selected.

Copy link
Contributor

coderabbitai bot commented Apr 14, 2025

"""

Walkthrough

A blank line was added after an early return in the get_selected_implementation_groups method of the ComplianceAssessment class without changing its logic. The audit report template was modified to conditionally display the "Selected implementation groups" section only if there are any groups to show.

Changes

File(s) Change Summary
backend/core/models.py Added a blank line after the early return in get_selected_implementation_groups method.
backend/core/templates/core/audit_report.html Wrapped the "Selected implementation groups" block in a conditional to render only if groups exist.

Poem

A blank line hops in, so neat and small,
In code’s quiet meadow, it stands tall.
The report now shows groups when they’re there,
Else hides the list with gentle care.
A rabbit’s tweak, subtle and bright,
Making the code just feel right! 🐇✨
"""


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Axxiar Axxiar marked this pull request as ready for review April 14, 2025 21:05
@Axxiar Axxiar marked this pull request as draft April 15, 2025 10:31
@Axxiar Axxiar marked this pull request as ready for review April 15, 2025 12:43
@eric-intuitem
Copy link
Collaborator

Perhaps there is a misunderstanding. When no IG is selected, the "IG" functionality is not used, so we use all requirements, regardless of IG. We don't need to list IGs in this situation, because we don't care for them.
I think this is the current behaviour, so probably no need to change.

Copy link
Collaborator

@Mohamed-Hacene Mohamed-Hacene left a comment

Choose a reason for hiding this comment

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

0k

@Axxiar Axxiar marked this pull request as draft June 12, 2025 15:56
@Axxiar Axxiar marked this pull request as ready for review June 13, 2025 10:13
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
backend/core/templates/core/audit_report.html (2)

42-51: Avoid redundant method invocations in template

The block calls compliance_assessment.get_selected_implementation_groups twice—first in the {% if %} and then again in the {% for %}—which may trigger duplicate queries or extra computation. Use a {% with %} to store the result and reuse it:

-{% if compliance_assessment.get_selected_implementation_groups %}
-  <div>
-      <p class='font-semibold'>{% trans "Selected implementation groups" %}</p>
-      <ul>
-          {% for group in compliance_assessment.get_selected_implementation_groups %}
-              <li>{{ group }}</li>
-          {% endfor %}
-      </ul>
-  </div>
-{% endif %}
+{% with selected_groups=compliance_assessment.get_selected_implementation_groups %}
+  {% if selected_groups %}
+    <div>
+      <p class='font-semibold'>{% trans "Selected implementation groups" %}</p>
+      <ul>
+        {% for group in selected_groups %}
+          <li>{{ group }}</li>
+        {% endfor %}
+      </ul>
+    </div>
+  {% endif %}
+{% endwith %}
🧰 Tools
🪛 HTMLHint (1.5.0)

[error] 44-44: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)


44-44: Use double quotes for HTML attributes

Per HTML standards (and to satisfy HTMLHint), attribute values should be wrapped in double quotes. Update the class attribute:

-<p class='font-semibold'>{% trans "Selected implementation groups" %}</p>
+<p class="font-semibold">{% trans "Selected implementation groups" %}</p>
🧰 Tools
🪛 HTMLHint (1.5.0)

[error] 44-44: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 85dec95 and 7a8e422.

📒 Files selected for processing (2)
  • backend/core/models.py (1 hunks)
  • backend/core/templates/core/audit_report.html (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • backend/core/models.py
🧰 Additional context used
🪛 HTMLHint (1.5.0)
backend/core/templates/core/audit_report.html

[error] 44-44: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
backend/core/templates/core/audit_report.html (1)

45-45: Use double quotes for HTML attributes
HTMLHint flagged the single quotes on the class attribute. Change to double quotes to satisfy lint rules.

Apply this diff:

-                <p class='font-semibold'>{% trans "Selected implementation groups" %}</p>
+                <p class="font-semibold">{% trans "Selected implementation groups" %}</p>
🧰 Tools
🪛 HTMLHint (1.5.0)

[error] 45-45: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a8e422 and 8384233.

📒 Files selected for processing (1)
  • backend/core/templates/core/audit_report.html (1 hunks)
🧰 Additional context used
🪛 HTMLHint (1.5.0)
backend/core/templates/core/audit_report.html

[error] 45-45: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)

⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: enterprise-startup-docker-compose-test
  • GitHub Check: startup-docker-compose-test
  • GitHub Check: enterprise-startup-functional-test (3.12)
  • GitHub Check: startup-functional-test (3.12)
  • GitHub Check: functional-tests (3.12, chromium)
  • GitHub Check: build (3.12)
  • GitHub Check: test (3.12)
  • GitHub Check: enterprise-functional-tests (3.12, chromium)
  • GitHub Check: Analyze (python)
🔇 Additional comments (1)
backend/core/templates/core/audit_report.html (1)

42-53: Conditional rendering of implementation groups is correct
Wrapping the "Selected implementation groups" block in a {% with %} and checking for selected_groups prevents empty sections from appearing when no groups are returned.

🧰 Tools
🪛 HTMLHint (1.5.0)

[error] 45-45: The value of attribute [ class ] must be in double quotes.

(attr-value-double-quotes)

@eric-intuitem eric-intuitem merged commit 92ed011 into main Jun 13, 2025
19 checks passed
@eric-intuitem eric-intuitem deleted the CA-947-empty-ig-on-export branch June 13, 2025 20:37
@github-actions github-actions bot locked and limited conversation to collaborators Jun 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants