fix: prevented infraMonitoring styles from overriding at other places

[SagarRajput-7]

Summary

• InfraMonitoring Styles had the antd cell override at the global place which effected and messed-up at other places - PlannedDowntime

Related Issues / PR's

• CSS style override causing layout issues on planned downtime page #7214

Screenshots

Before:

Screen.Recording.2025-03-24.at.8.50.11.PM.mov

After:

Screen.Recording.2025-03-24.at.8.49.13.PM.mov

Affected Areas and Manually Tested Areas

---

Important

Scopes table cell styles to .infra-monitoring-container in InfraMonitoringK8s.styles.scss to prevent global overrides.

• Styles:
  • Wraps .ant-table-cell styles within .infra-monitoring-container to prevent global overrides in InfraMonitoringK8s.styles.scss.
  • Moves .ant-table-row-expand-icon-cell styles under .expanded-k8s-list-table within .infra-monitoring-container.
• Behavior:
  • Ensures table cell styles are scoped to the infra monitoring component, preventing unintended style application elsewhere.

^{This description was created by for 36aa003. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 36aa003 in 1 minute and 19 seconds

More details

• Looked at 71 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 7 drafted comments based on config settings.

1. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:711

• Draft comment:
  Usage of :has() pseudo-class is modern but verify browser support meets target requirements.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to verify browser support for the :has() pseudo-class, which is not allowed as per the rules. It doesn't provide a specific suggestion or point out a clear issue with the code.

2. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:705

• Draft comment:
  Good encapsulation: Wrapping the table cell overrides in .infra-monitoring-container limits the scope and prevents leaking styles globally.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:707

• Draft comment:
  Consider reducing the use of !important if possible to improve maintainability, unless absolutely necessary to override external library styles.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:712

• Draft comment:
  Ensure the browser support for the CSS :has pseudo-class meets our target requirements, as its support can be limited.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to ensure browser support for a CSS feature, which falls under the category of asking the author to double-check or verify something. This violates the rule against asking the author to confirm or ensure things.

5. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:706

• Draft comment:
  There are multiple separate .ant-table-cell blocks; consider consolidating them to reduce duplication and improve clarity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

6. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:736

• Draft comment:
  Double-check that both the nested rule within .expanded-k8s-list-table and the standalone .ant-table-row-expand-icon-cell rule are required to cover all cases without unintended side effects.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

7. frontend/src/container/InfraMonitoringK8s/InfraMonitoringK8s.styles.scss:768

• Draft comment:
  Typographical error: 'background-color: none !important;' is not a valid CSS value. Consider replacing it with 'background-color: transparent !important;' to ensure correct styling.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_dUqIWsoadOaLMNmA

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.