JACoB PR for Issue Case Insensitivity Bug in Code Visualization Component with Custom Taxonomies

[jacob-ai-bot[bot]]

Summary:

Description

The code visualization component incorrectly handles custom taxonomies in a case-insensitive manner. Specifically, when creating the context using custom taxonomies, the component treats taxonomies with uppercase and lowercase versions as separate file paths. This behavior should be case-insensitive, consolidating them into a single file path.

Steps to Reproduce

1. Navigate to the code visualization component in the application.
2. Choose a codebase with a custom taxonomy with both uppercase and lowercase letters, e.g., Category and category.
3. Observe how the component generates file paths for these taxonomies.

Expected Behavior

Custom taxonomies should be treated case-insensitively, meaning Category and category should result in a single, unified file path.

Actual Behavior

The component treats Category and category as two separate file paths, leading to duplicated or fragmented paths.

Error Messages

No specific error messages are logged, but the UI reflects the incorrect file path handling.

Impact

This bug can lead to confusion and inefficiency in navigating code structures, as users may encounter redundant or inconsistent file paths due to case variations in taxonomies.

Suggested Fix

Locate and modify the case handling logic in the front end to ensure that custom taxonomies are treated in a case-insensitive manner, consolidating uppercase and lowercase versions into a single file path.

---

@jacob-ai-bot

Plan:

Step 1: Edit /src/app/dashboard/[org]/[repo]/code-visualizer/codebase/CodebaseVisualizer.tsx

Task: Modify CodebaseVisualizer for case-insensitive taxonomy handling

Instructions: Update the code in '/src/app/dashboard/[org]/[repo]/code-visualizer/codebase/CodebaseVisualizer.tsx' to ensure that taxonomy comparisons are case-insensitive. This involves:

• Modifying any instances where taxonomy strings are compared using methods like 'startsWith' and 'includes', by converting both the taxonomy strings and the comparison strings to lowercase before performing the comparison.

• Updating the 'processContextItems' function to handle taxonomy strings in a case-insensitive manner when constructing the tree data. Ensure that taxonomy paths are compared and aggregated without considering case differences, but preserve the original casing for display purposes.

Ensure that these changes result in taxonomies with different casing being treated as the same, consolidating them into a single file path, and eliminating duplicated or fragmented paths caused by case differences.

Exit Criteria: The code visualization component correctly consolidates taxonomies regardless of case differences, and users no longer experience duplicated or fragmented paths due to case variations in taxonomies. Original casing of taxonomies is preserved in the display.

Step 2: Edit /src/app/utils.ts

Task: Add case-insensitive string comparison utility functions

Instructions: In '/src/app/utils.ts', add utility functions for case-insensitive string comparisons, such as 'startsWithIgnoreCase' and 'includesIgnoreCase'. These functions should perform string comparisons without considering case differences. Refactor the CodebaseVisualizer component to use these utility functions for taxonomy comparisons, ensuring consistent and maintainable code for case-insensitive handling.

Exit Criteria: Utility functions for case-insensitive string comparisons are implemented and utilized in the CodebaseVisualizer component, providing consistent case-insensitive handling of taxonomies throughout the codebase.

[jacob-ai-bot[bot]]

Hello human! 👋

This PR was created by JACoB to address the issue Case Insensitivity Bug in Code Visualization Component with Custom Taxonomies

Next Steps

1. Please review the PR carefully. Auto-generated code can and will contain subtle bugs and mistakes.

2. If you identify code that needs to be changed, please reject the PR with a specific reason. Be as detailed as possible in your comments. JACoB will take these comments, make changes to the code and push up changes. Please note that this process will take a few minutes.

3. Once the code looks good, approve the PR and merge the code.