Conversation
|
Actually this was the behavior from the prompt management and quick skills editor. That allows users to edit the prompts when needed. |
| updated(changed) { | ||
| if (changed.has('messages')) { | ||
| const log = this.shadowRoot.querySelector('.chat-messages-container'); | ||
| const log = this.shadowRoot.querySelector('.chat-scroll-container'); |
There was a problem hiding this comment.
Should we move selectors we're querying to constants to prevent regressions?
There was a problem hiding this comment.
Indeed, this is a recurring pattern. Will create a followup PR to collate all such usages across chat.
I don't think it's confusing (although I'm not sure I understand what selecting a tool from the / menu will do), but I think it's too many clicks to run a prompt - click +, click prompts, select prompt Vs if we integrated it with the / menu (slash would be combo of commands and skills), it's just type / and select prompt. |
Regarding clicks, true I agree. But then the slash menu becomes a pot of all different things ie prompts,commands,skills so that would need to be much cleaner and clearer than what we have atm. I would say we keep it as is for now, and follow up from the ux side whether these should also be present within the / menu. Adding it should be straightforward if we decide to do so anyway. |
|
@sharanyavinod Do you want to start writing e2e tests with this feature? |
Do we start already, or post move to da live? cc @hannessolo |
|
I was also thinking - instead of a magical / which does everything, why not something like slack ie type/ shows the different options like /prompt /skill etc and selecting that opens the follow up menu with filter search etc like we have prompts today. Just an easier way of triggering prompts and others aligned to existing standards, and already includes control if any of these lists grows too much without overwhelming the end user. Thoughts? Of course, nothing to be considered within the scope of this PR but more for when we implement slash menu. |
I don't mind. Before we merge to da-live the tests are quite decoupled anyway. |
|
In the Screenshot it says "DA Commands" this should be "Experience Workspace Commands" or if too long maybe just "Commands". |
I don't think the slash menu is implemented yet, that screenshot is from figma. We discussed in the daily today that we hold off the slash menu for now until we clarify where which types of items should show up (and whether we even need skills vs commands). |
|
@anfibiacreativa I discussed with @hannessolo as well, and I feel it might be too complicated to already start with tests while our changes are still across repos/branches. Would prefer to hold on adding them, until after we move to da-live. |

Includes:
Preview available at https://da.live/canvas?nx=ew-prompts&nxver=2#/aem-sandbox/block-collection/ew-test