Merge in AI changes to this branch

[jmgasper]

No description provided.

[github-actions]

[💡 readability]
The viewBox attribute contains very high precision floating-point numbers, which might be unnecessary and could impact readability. Consider simplifying these values if such precision is not required for the rendering of the SVG.

[github-actions]

[⚠️ accessibility]
The SVG element lacks a title or desc tag for accessibility. Consider adding these to improve accessibility for screen readers.

[github-actions]

[💡 accessibility]
The text element with x="-9999" and y="-9999" is used to hide text for accessibility purposes. While this is a common technique, ensure that it is necessary and that it does not interfere with other accessibility features.

[github-actions]

[💡 style]
The SVG file is missing a newline at the end of the file. While this is not a functional issue, it's a good practice to include a newline at the end of files to avoid potential issues with some tools and to adhere to POSIX standards.

[github-actions]

[💡 style]
The file is missing a newline at the end. While this is a minor issue, it is generally a good practice to include a newline at the end of files for compatibility with various tools and to adhere to POSIX standards.

[github-actions]

[❗❗ correctness]
The endpoint URL has been changed from /payments/challenges/ to /finance/challenge-payments/. Ensure that the new endpoint is correct and that the backend service supports this path, as this could lead to a runtime error if the endpoint does not exist.

[github-actions]

[❗❗ correctness]
The API version in the endpoint URL has been updated from V5 to V6. Verify that the API version V6 is deployed and compatible with the expected payload structure and response format. This change could break functionality if the API version is not correctly supported.

[github-actions]

[💡 maintainability]
The fill-rule and clip-rule attributes are used here, but it's not clear if they are necessary for the visual outcome of this SVG. If they are not needed, consider removing them to simplify the SVG markup.

[github-actions]

[💡 maintainability]
Consider using a more descriptive id or class attribute for the <path> element to enhance maintainability and facilitate future styling or scripting changes.

[github-actions]

[💡 maintainability]
The SVG path data is quite complex and could benefit from being split into multiple lines or using a tool to simplify the path. This would improve readability and maintainability.

[github-actions]

[💡 readability]
Consider using a more descriptive id for the clipPath element instead of clip0_2793_151. This will make it easier to understand and manage if more clip paths are added in the future.

[github-actions]

[⚠️ correctness]
The phasesIcons object uses the same IconReview component for both 'iterative review' and 'review' keys. Ensure this is intentional and that both phases should indeed use the same icon.

[github-actions]

[⚠️ correctness]
The use of Sass variables like $sp-2 and $sp-4 for padding is good for consistency, but ensure these variables are defined and imported correctly to avoid runtime errors.

[github-actions]

[⚠️ design]
The max-width of 200px for .workflowName > div:first-child might cause truncation issues on smaller screens. Consider using a relative unit or media queries to handle different screen sizes more gracefully.

[github-actions]

[💡 maintainability]
Consider using a constant for the tablet breakpoint value 984 to improve maintainability and avoid magic numbers.

[github-actions]

[❗❗ correctness]
The submittedDate property is accessed on props.submission without being explicitly defined in the AiReviewsTableProps interface. Ensure submittedDate is part of the BackendSubmission type or adjust the type accordingly.

[github-actions]

[⚠️ correctness]
The URL path ./ai-scorecard/${props.submission.id}/${run.workflow.id} assumes run.workflow.id is always defined. Consider adding a check to ensure run.workflow.id is not undefined to prevent potential runtime errors.

[github-actions]

[❗❗ correctness]
Ensure that $teal-160 is defined in the imported styles. If it's missing or incorrect, it could lead to unexpected styling issues.

[github-actions]

[❗❗ correctness]
Ensure that $black-20 is defined in the imported styles. If it's missing or incorrect, it could lead to unexpected styling issues.

[github-actions]

[⚠️ performance]
The useMemo hook is used here, but the dependency array only includes props.run.status. If props.run is a new object on each render, this could lead to unnecessary recalculations. Consider using props.run as the dependency if the entire object is stable, or ensure that props.run.status is the only relevant dependency.

[github-actions]

[⚠️ performance]
Similar to the previous comment, the useMemo hook's dependency array only includes props.run.status. Ensure that this is the only relevant dependency, or consider using props.run if the entire object is stable to avoid unnecessary recalculations.

[github-actions]

[💡 design]
The icon size class icon-md is used here, while other statuses use icon-xl. Ensure that this difference in icon size is intentional and consistent with the design requirements.

[github-actions]

[💡 maintainability]
The StatusLabel component for the failed status does not include the hideLabel prop. If this omission is intentional, ensure that it aligns with the design requirements. Otherwise, consider adding hideLabel={props.hideLabel} for consistency.

[github-actions]

[❗❗ correctness]
The color variable $teal-160 is used here, but it's not clear if this variable is defined in the imported styles. Ensure that $teal-160 is defined to avoid potential issues with undefined variables.

[github-actions]

[❗❗ correctness]
Using props.score in a conditional check will render 0 as false. Consider using props.score !== undefined to ensure 0 is displayed correctly.

[github-actions]

[⚠️ correctness]
Consider using props.label && !props.hideLabel to ensure that the label is only rendered when it is defined.

[github-actions]

[⚠️ correctness]
The use of non-null assertion (!!r.aiWorkflowId) in the filter function could lead to unexpected behavior if aiWorkflowId is 0 or false. Consider using a more explicit check, such as r.aiWorkflowId != null, to ensure that only non-null and non-undefined values are included.

[github-actions]

[⚠️ compatibility]
The use of tr:has(&) is a relatively new CSS selector and might not be supported in all browsers. Ensure that the target browsers for this application support this feature, or consider providing a fallback for unsupported browsers.

[github-actions]

[❗❗ correctness]
Using the non-null assertion operator (!) on props.aiReviewers can lead to runtime errors if aiReviewers is undefined. Consider adding a check to ensure aiReviewers is defined before using it.

[github-actions]

[💡 readability]
The expression allRows ? !allRows.indexOf(submission) : false is used to determine the defaultOpen state. This logic might not be clear at first glance. Consider refactoring this to improve readability, such as using a named function or variable to explain the intent.

[github-actions]

[❗❗ correctness]
Typo in class name .reviewersDropown. It should likely be .reviewersDropdown.

[github-actions]

[❗❗ correctness]
The calculation of aiReviewersCount includes an additional 1 without any explanation. If this is intentional, consider clarifying why an extra reviewer is counted. If not, it may lead to incorrect display logic.

[github-actions]

[⚠️ correctness]
The class name styles.reviewersDropown seems to have a typo. It should likely be styles.reviewersDropdown. This could lead to styling issues if the class is not applied correctly.