sendingtk / chatwoot

Other
52 stars 74 forks source link

feat: Actualizar configuración del plugin de sugerencias de emojis #132

Closed nestordavalos closed 2 months ago

nestordavalos commented 2 months ago

Actualiza la configuración del plugin de sugerencias de emojis en el componente Editor.vue para que se active después de escribir al menos 2 caracteres después de ":" en lugar de 1.

También se actualiza el componente keyboardEmojiSelector.vue para cargar los emojis de acuerdo con los nuevos grupos de emojis y realizar una búsqueda sin espacios en blanco y en minúsculas.

Además, se agrega un hook beforeRouteLeave en el componente ConversationView.vue para limpiar el estado seleccionado al navegar lejos de una conversación y evitar problemas de datos obsoletos.

Estos cambios mejoran la experiencia del usuario al utilizar el editor de texto y al navegar por las conversaciones.

Summary by CodeRabbit

coderabbitai[bot] commented 2 months ago

Walkthrough

The changes involve modifications to the Editor.vue, keyboardEmojiSelector.vue, and ConversationView.vue components. The suggestionsPlugin in Editor.vue now requires two characters after a colon for suggestions. The keyboardEmojiSelector.vue has renamed the emoji data import and updated how emojis are processed and displayed. Additionally, ConversationView.vue introduces a beforeRouteLeave lifecycle hook to clear the selected state in the Vuex store when navigating away from a conversation.

Changes

File Path Change Summary
app/javascript/dashboard/components/widgets/WootWriter/Editor.vue Modified matcher in suggestionsPlugin to require two characters after a colon for suggestions.
app/javascript/dashboard/components/widgets/WootWriter/keyboardEmojiSelector.vue Renamed imported emoji data from emojis to emojiGroups, updated emoji data processing, and changed display from slug to name.
app/javascript/dashboard/routes/dashboard/conversation/ConversationView.vue Added beforeRouteLeave lifecycle hook to clear selected state in Vuex store on navigation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Editor
    participant SuggestionsPlugin
    participant EmojiSelector
    participant ConversationView
    participant VuexStore

    User->>Editor: Types ':a'
    Editor->>SuggestionsPlugin: Check for suggestions
    SuggestionsPlugin-->>Editor: No suggestions (requires 2 characters)

    User->>EmojiSelector: Searches for emoji
    EmojiSelector->>EmojiData: Load and process emojis
    EmojiData-->>EmojiSelector: Return processed emojis
    EmojiSelector-->>User: Display emojis by name

    User->>ConversationView: Navigates away
    ConversationView->>VuexStore: Dispatch clearSelectedState
    VuexStore-->>ConversationView: State cleared

Poem

In the garden of code, changes bloom bright,
With emojis that dance, and suggestions in sight.
A rabbit hops by, with a twitch of delight,
For clearer paths forward, and states that feel right.
So let’s celebrate progress, with a hop and a cheer,
In this world of our making, we hold dear! 🐇✨

[!TIP]

OpenAI O1 model for chat - We have deployed OpenAI's latest O1 model for chat. - OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model. - Please share any feedback with us in the [discussions post](https://discord.com/channels/1134356397673414807/1283929536186155099).

Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between 93102e6af2cb44642b1d31cfa84b73133668530b and 366b85a30b8598118e68f542516232d858ffee71.
Files selected for processing (3) * app/javascript/dashboard/components/widgets/WootWriter/Editor.vue (1 hunks) * app/javascript/dashboard/components/widgets/WootWriter/keyboardEmojiSelector.vue (3 hunks) * app/javascript/dashboard/routes/dashboard/conversation/ConversationView.vue (1 hunks)
Additional comments not posted (6)
app/javascript/dashboard/components/widgets/WootWriter/keyboardEmojiSelector.vue (4)
`3-3`: **LGTM!** The change in the import statement from `emojis` to `emojiGroups` improves clarity and aligns with the naming convention used in the rest of the code. --- `26-31`: **LGTM!** The changes in the `loadEmojis` function improve the handling of emoji data: - Destructuring the `name` and `slug` properties allows for more explicit usage of these properties. - Constructing the `searchString` by removing whitespace and converting to lowercase ensures consistency in the search terms, which may enhance search functionality. --- `65-65`: **LGTM!** Displaying the `name` instead of the `slug` for each emoji improves user experience by providing a more recognizable identifier. --- Line range hint `1-71`: **Overall, the changes in this file are well-implemented and improve the clarity and functionality of the emoji selector component.** The key improvements include: - Renaming the imported emoji data for better clarity. - Updating the logic for flattening and transforming the emoji data to handle the `name` and `slug` properties more explicitly. - Enhancing the search functionality by removing whitespace and converting to lowercase for the `searchString`. - Displaying the `name` instead of the `slug` for each emoji to improve user experience. Great job with these changes!
app/javascript/dashboard/routes/dashboard/conversation/ConversationView.vue (1)
`18-25`: **LGTM!** The new `beforeRouteLeave` lifecycle hook is implemented correctly. It clears the selected state in the Vuex store when navigating away from a conversation with an associated `conversationId`, preventing stale data issues and resolving timing problems during navigation. The logic of dispatching the `clearSelectedState` action only when `this.conversationId` is present ensures the state is cleared appropriately. Calling `next()` after the conditional block allows the navigation to proceed as expected. The code comments provide clear explanations of the purpose and behavior of this lifecycle hook.
app/javascript/dashboard/components/widgets/WootWriter/Editor.vue (1)
`250-250`: **Refined emoji suggestion trigger** Updating the `matcher` to require at least 2 characters after the colon (`:`) is a good enhancement. It will help reduce premature suggestions and make the emoji suggestions more contextually relevant, improving the user experience.
--- 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 - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - 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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.