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

🔚 Move end block to block list #355

Closed
njoroge-jane opened this issue Mar 15, 2023 · 1 comment · Fixed by #380
Closed

🔚 Move end block to block list #355

njoroge-jane opened this issue Mar 15, 2023 · 1 comment · Fixed by #380
Labels
1-pointer Simple class issue - 1 bounty points enhancement New feature or request

Comments

@njoroge-jane
Copy link
Collaborator

njoroge-jane commented Mar 15, 2023


Quick links: Summary | Description | Template | Example | Resources


Summary

As a user of the CLM bot, I want the end block to be moved to the block list so that I can easily find it and use it when building conversational flows.

Description

Currently, the end block for the CLM appears in the bot editor frame. This can make it confusing for users who are trying to build conversational flows with the bot. It would be helpful if the end block could be moved to the block list.

Moving the end block to the block list will make it easier for users to find and use when building conversational flows. It will also improve the overall user experience for the bot.

Template

### Acceptance Criteria

1. If I open the active bot workspace in the CLM.
1. The end block is moved from the bot editor frame to the block list.
1. The end block is clearly labeled as the end block.
1. The end block is easily accessible from the block list.
1. The user is able to use the end block to successfully end a conversation flow.
1. The functionality of the end block remains the same. 


### Resources:

* CLM Code Base: [GitHub repository for the conversational learning manager](https://github.com/italanta/elewa) ;

### [Notes]

Please also note:

If a conversation about the issue I’m working on is happening,
the outcomes should be documented within that issue (not in the comments).


* Once someone picks up this issue, they should provide an update at least every 3 days to ensure that assistance can be provided if necessary.

@njoroge-jane njoroge-jane added the enhancement New feature or request label Mar 15, 2023
@Beulah-Matt
Copy link
Collaborator

Working on this

@ReaganCn ReaganCn added the 1-pointer Simple class issue - 1 bounty points label Mar 27, 2023
ReaganCn added a commit that referenced this issue Mar 28, 2023
…lockList

🎨 Move End Block to Block List #355
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-pointer Simple class issue - 1 bounty points enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants