EPMRPP-104838 || Visibility of Privacy Policy link in sidebar dependi…

[BlazarQSO]

…ng on instance type

PR Checklist

• Have you verified that the PR is pointing to the correct target branch? (develop for features/bugfixes, other if mentioned in the task)
• Have you verified that your branch is consistent with the target branch and has no conflicts? (if not, make a rebase under the target branch)
• Have you checked that everything works within the branch according to the task description and tested it locally?
• Have you run the linter (npm run lint) prior to submission? Enable the git hook on commit in your IDE to run it and format the code automatically.
• Have you run the tests locally and added/updated them if needed?
• Have you checked that app can be built (npm run build)?
• Have you checked that no new circular dependencies appreared with your changes? (the webpack plugin reports circular dependencies within the dev npm script)
• Have you made sure that all the necessary pipelines has been successfully completed?
• If the task requires translations to be updated, have you done this by running the manage:translations script?
• Have you added the link to the PR in the Jira ticket comments?

Visuals

Summary by CodeRabbit

• New Features
  • The privacy policy link in the sidebar footer is now shown only for specific application instance types.

[coderabbitai]

Walkthrough

The sidebar footer in the application was updated to conditionally display the privacy policy link. Now, the link is shown only when the application instance type is either SAAS or EPAM, determined by imported selectors and constants. No changes were made to the component's exports or props.

Changes

File(s)	Change Summary
app/src/layouts/common/appSidebar/appSidebar.jsx	Conditional rendering added for the privacy policy link in the sidebar footer based on instance type.

Poem

In the sidebar's gentle light,
A privacy link takes flight—
But only if the instance calls
For SAAS or EPAM in its halls.
With careful checks, the code is neat,
A rabbit’s hop, a tidy feat!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4c7f1e0 and 8f4c22e.

📒 Files selected for processing (1)

• app/src/layouts/common/appSidebar/appSidebar.jsx (3 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: Guria
PR: reportportal/service-ui#4403
File: app/src/pages/inside/testCaseLibraryPage/emptyState/emptyStateDetails.tsx:30-36
Timestamp: 2025-06-12T00:09:07.409Z
Learning: During the mock stage of UI work in reportportal/service-ui, it is acceptable for interactive elements (e.g., buttons) to omit functional handlers such as `onClick`; these will be implemented in subsequent merge requests. Review comments should avoid flagging these omissions unless the implementation MR is in scope.

app/src/layouts/common/appSidebar/appSidebar.jsx (2)

Learnt from: Guria
PR: reportportal/service-ui#4385
File: app/src/components/testCaseList/testCaseNameCell/testCaseNameCell.tsx:30-42
Timestamp: 2025-06-09T17:12:07.281Z
Learning: In React components, static objects like icon mappings that don't depend on props or state should be defined outside the component function to avoid unnecessary re-creation on every render, improving performance.

Learnt from: Guria
PR: reportportal/service-ui#4407
File: app/src/pages/common/popoverControl/popoverControl.tsx:55-63
Timestamp: 2025-06-13T21:54:46.839Z
Learning: The Popover component from '@reportportal/ui-kit' handles closing internally when items are clicked, so manual closing via setIsOpened(false) in onClick handlers is not needed.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Call feature Docker build / Build and export to AWS ECR
• GitHub Check: build (20)
• GitHub Check: build (20)

🔇 Additional comments (3)

app/src/layouts/common/appSidebar/appSidebar.jsx (3)

28-29: LGTM! Clean import organization.

The new imports follow the established patterns and are properly grouped with other Redux-related imports.

---

52-53: Well-implemented conditional logic.

The instance type checking follows React/Redux best practices with clear variable naming and straightforward boolean logic.

---

68-80: Excellent conditional rendering implementation.

The privacy policy block is properly wrapped with conditional logic while preserving all existing functionality including analytics tracking, internationalization, and external link handling.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feauter/EPMRPP-104838-visibility-of-privacy-policy

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 auto-generate unit tests to generate unit tests for 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.80%. Comparing base (0d94cf2) to head (8f4c22e).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4469      +/-   ##
===========================================
- Coverage    67.20%   66.80%   -0.41%     
===========================================
  Files           84       84              
  Lines          991      997       +6     
  Branches       140      140              
===========================================
  Hits           666      666              
- Misses         294      300       +6     
  Partials        31       31              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.