Skip to content

Conversation

@pratikb64
Copy link
Contributor

@pratikb64 pratikb64 commented Oct 10, 2025

This PR introduces the Profile and General Settings module in the settings modal, enhancing user customization and application management capabilities. Additionally, it adds search functionality to all list views, enabling users to search and locate items quickly.

Highlights

  • New Profile Page: Dedicated page for users to view and manage their profile information.
  • General Settings Page: Centralized location for adjusting application-wide preferences.
  • Search Bars for Lists: Added search input fields to all list components for improved usability and faster navigation.
  • UI Polish: Fixed various spacing inconsistencies across the application for a cleaner, more consistent layout.

Changelog

  • Created ProfilePage and GeneralSettingsPage components with routing
  • Added Search bar for all list views, it shows when there are more than 10 items
  • Adjusted margins, paddings, and alignments to resolve spacing issues
  • Updated sidebar to include profile and general settings module
2025-10-10.18-30-09.mp4

Fixes #2486

<div class="relative">
<Input
v-model="assignmentRuleSearchQuery"
@input="assignmentRuleSearchQuery = $event"
Copy link
Member

Choose a reason for hiding this comment

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

why is @input needed when we have v-model?

Copy link
Contributor Author

@pratikb64 pratikb64 Nov 3, 2025

Choose a reason for hiding this comment

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

@input is required because Input component updates model value on blur, changed v-model to :model-value

<script setup lang="ts">
import AddNewAgentsDialog from "@/components/desk/global/AddNewAgentsDialog.vue";
import { assignmentRuleData } from "@/stores/assignmentRules";
import {
Copy link
Member

Choose a reason for hiding this comment

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

can we skip using headless?

any other way to achieve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Email Account setup form not scrollable - bottom fields cutoff

2 participants