Skip to content

Conversation

@EkamBhullar
Copy link

Ontrack Component Review

Team Member Name

Ekamjot Singh
224235519

Component Name

group-selector

Files in this component:

  • group-selector.component.ts
  • group-selector.component.html
  • group-selector.component.scss

Component Purpose

The group-selector component is designed to allow users (typically staff) to view, edit, and manage student tutorial groups within a unit. It presents a table where each row represents a group, displaying attributes like name, tutorial association, capacity, and lock status.
Users can click to edit the group’s details inline using input fields or dropdowns. The interface supports toggling lock status, saving or canceling edits, and deleting groups.

Component Outcomes and Interactions

Expected Outcomes:

  • View a list of groups in a unit
  • Edit group name, tutorial association, and capacity
  • Save or cancel group edits
  • Lock/unlock a group
  • Delete a group

Interactions:

  • Input: Accepts a unit object that includes groups and tutorials
  • Output: Emits updated group data back to parent or backend service
  • Services: May use UnitService, GroupService, and related observables for saving and deleting

Component Migration Plan

Migration Goals:

  • Migrate from Angular Material + Bootstrap to Tailwind CSS
  • Improve accessibility and responsiveness
  • Ensure smooth inline editing without layout shifts

Steps:

  1. Analyze current HTML and styling
  2. Replace UI elements with Tailwind CSS equivalents (input, select, button)
  3. Use Tailwind spacing and transition utilities for stable layout
  4. Ensure responsive design using Tailwind’s flex/grid utilities
  5. Update Angular bindings ([(ngModel)] or ReactiveForms)
  6. Validate UI and UX with mock data

###Before
image

@LovleenKala
Copy link

Great job on the component review! You've clearly outlined the purpose of the group-selector component, including its core functionalities like group viewing, editing, and management. The detailed breakdown of expected outcomes and interactions demonstrates a strong understanding of the component's role within OnTrack.

@HasinduWelarathne
Copy link

Great work, Ekam! Your component review is well-structured, and easy to follow. The purpose, outcomes, and migration Plan sections clearly tell what needs to happen and why, and your step-by-step Tailwind migration roadmap is solid. I have no blocking concerns, so I’m happy to approve this PR.

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.

3 participants