Skip to content
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

JNG-5983 tag navigation #477

Merged
merged 1 commit into from
Oct 29, 2024
Merged

Conversation

noherczeg
Copy link
Contributor

@noherczeg noherczeg commented Oct 28, 2024

BugJNG-5983 Navigation doesn't work on Tag Components on View Page

Copy link

coderabbitai bot commented Oct 28, 2024

Walkthrough

The changes in the pull request focus on the Tags component within the Tags.tsx.hbs file. The modifications include the addition of an onClick event handler to the Chip component, allowing for user interaction. The sx prop is introduced to conditionally set the cursor style based on the presence of the onItemClick function and the edit mode status. Additionally, the ChipProps object has been removed from the Autocomplete component, streamlining the click handling for chips. The overall component structure and error handling remain unchanged.

Changes

File Path Change Summary
judo-ui-react/src/main/resources/actor/src/components/widgets/Tags.tsx.hbs Modified Chip component to include onClick event handler and added sx prop for cursor styling. Removed ChipProps from Autocomplete, integrating click functionality directly into Chip.

Poem

In the garden of clicks, where the chips play,
A new handler dances, brightening the day.
With a flick of the cursor, they spring into action,
Enhancing our joy with each little interaction.
Hops of delight in the user’s embrace,
A whimsical change in this vibrant space! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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.

Copy link

@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: 2

🧹 Outside diff range and nitpick comments (1)
judo-ui-react/src/main/resources/actor/src/components/widgets/Tags.tsx.hbs (1)

216-216: Consider using CSS classes for cursor styling.

The current approach mixes styling concerns with component logic. Consider using CSS classes for better separation of concerns and maintainability.

Here's a suggested improvement:

-sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
+className={clsx({
+  'clickable-tag': typeof onItemClick === 'function' && !editMode,
+})}

Add this CSS class to your stylesheet:

.clickable-tag {
  cursor: pointer;
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 45340c2 and e5f1d49.

📒 Files selected for processing (1)
  • judo-ui-react/src/main/resources/actor/src/components/widgets/Tags.tsx.hbs (1 hunks)

Comment on lines +212 to +218
return <Chip
key={key}
label={option[autoCompleteAttribute]}
{...rest}
sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
onClick={onChipClicked}
/>;
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider using data attributes for more reliable click handling.

The current implementation relies on textContent to find the clicked tag, which could be fragile if the label text is not unique. Consider using data attributes for more reliable click handling.

Here's a suggested improvement:

 return <Chip
   key={key}
   label={option[autoCompleteAttribute]}
   {...rest}
   sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
-  onClick={onChipClicked}
+  data-tag-id={option[identifierAttribute]}
+  onClick={(event) => {
+    if (onItemClick && !editMode) {
+      const tagId = (event.currentTarget as HTMLElement).dataset.tagId;
+      const data = values.find((c: any) => c[identifierAttribute] === tagId);
+      if (data) {
+        onItemClick(data);
+      }
+    }
+  }}
 />;

This approach:

  • Uses data attributes to store the tag identifier
  • Moves the click logic inline for better type safety
  • Removes the need for textContent matching

Committable suggestion was skipped due to low confidence.


🛠️ Refactor suggestion

Enhance accessibility for clickable tags.

When tags are clickable (onItemClick present and not in edit mode), they should be properly marked as interactive elements for accessibility.

Add these accessibility attributes:

 return <Chip
   key={key}
   label={option[autoCompleteAttribute]}
   {...rest}
   sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
   onClick={onChipClicked}
+  role={onItemClick && !editMode ? "button" : undefined}
+  tabIndex={onItemClick && !editMode ? 0 : undefined}
+  onKeyDown={(e) => {
+    if (onItemClick && !editMode && (e.key === 'Enter' || e.key === ' ')) {
+      e.preventDefault();
+      onChipClicked(e as any);
+    }
+  }}
 />;

This enhancement:

  • Adds proper role for screen readers
  • Enables keyboard navigation
  • Handles keyboard events (Enter/Space) for activation
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
return <Chip
key={key}
label={option[autoCompleteAttribute]}
{...rest}
sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
onClick={onChipClicked}
/>;
return <Chip
key={key}
label={option[autoCompleteAttribute]}
{...rest}
sx={ { cursor: (typeof onItemClick === 'function' && !editMode) ? 'pointer' : undefined } }
onClick={onChipClicked}
role={onItemClick && !editMode ? "button" : undefined}
tabIndex={onItemClick && !editMode ? 0 : undefined}
onKeyDown={(e) => {
if (onItemClick && !editMode && (e.key === 'Enter' || e.key === ' ')) {
e.preventDefault();
onChipClicked(e as any);
}
}}
/>;

@noherczeg noherczeg merged commit 7f821a6 into develop Oct 29, 2024
3 checks passed
@noherczeg noherczeg deleted the bugfix/JNG-5983-tag-navigation branch October 29, 2024 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants