Skip to content

Conversation

@AdityaHegde
Copy link
Collaborator

@AdityaHegde AdityaHegde commented Dec 10, 2025

Adds the mention-like inline context to developer chat.
Adds models and their columns to dev chat for rill developer context. This is the 1st iteration, we will probably add more of these.

Known issue: Using keyboard to move to model doesnt automatically uncollapse it because the options are not loaded. Will do a follow up that does some significant changes to the highlight manager in a separate PR.

Checklist:

  • Covered by tests
  • Ran it and it works as intended
  • Reviewed the diff before requesting a review
  • Checked for unhandled edge cases
  • Linked the issues it closes
  • Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
  • Intend to cherry-pick into the release branch
  • I'm proud of this work!

@AdityaHegde AdityaHegde force-pushed the feat/mention-support-in-dev-chat branch from bc6dfb2 to 5c2dade Compare December 17, 2025 12:58
@AdityaHegde AdityaHegde force-pushed the feat/mention-support-in-dev-chat branch from 6a974a3 to ec43819 Compare December 17, 2025 13:24
@AdityaHegde AdityaHegde marked this pull request as ready for review December 17, 2025 13:26
@AdityaHegde AdityaHegde force-pushed the feat/mention-support-in-dev-chat branch from 0096f76 to 58e7844 Compare December 19, 2025 07:10
@AdityaHegde AdityaHegde force-pushed the feat/mention-support-in-dev-chat branch from 58e7844 to 1f28f16 Compare December 19, 2025 07:16
@ericokuma
Copy link
Contributor

Screenshot 2025-12-19 at 10 55 56 AM Not sure I like the up/down arrow icon here. Is this to indicate you can expand/collapse? If so it might be better to just have the >/v indicators in front of the resource name

Copy link
Contributor

@ericpgreen2 ericpgreen2 left a comment

Choose a reason for hiding this comment

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

UXQA: I'm finding it very hard to use the keyboard to move around in the dropdown menu.

  1. I type @ to open the menu, I press the down arrow, and I'd expect to move to the second item in the list. Instead, the first metrics view is "opened" and a measure is in focus. Further, sometimes I've found that it focuses a random measure (e.g. see the second image below), not the first one in the list. For inspiration, Cursor does a good job with keyboard navigation in their context picker.
    Image
    Image
  2. Sometimes I have to hit the up/down arrow key twice in order to navigate to the next item in the dropdown menu
  3. When I type @ad, I see "No matches found". That messaging makes it feel like there's nothing to select. But, in fact, in this case, I can select the metrics view or the model. We should be more specific about what's "not found".
    Image
  4. The resource icons disappear when the resource is in the expanded state (see image above)

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.

5 participants