Skip to content

P0072 | Orginazation details script #430

Merged
Chandan-walker merged 2 commits intodevelopmentfrom
P0072-test
Feb 23, 2026
Merged

P0072 | Orginazation details script #430
Chandan-walker merged 2 commits intodevelopmentfrom
P0072-test

Conversation

@Chandan-walker
Copy link
Collaborator

No description provided.

Copy link

@windsurf-bot windsurf-bot bot left a comment

Choose a reason for hiding this comment

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

💡 To request another review, post a new comment with "/windsurf-review".

Comment on lines +233 to +255
// .mat-form-field-disabled.timezone-field,
// .mat-form-field .mdc-text-field--disabled {
// opacity: 0.7;

// .mat-select-value,
// .mat-select-value-text,
// .mat-input-element,
// mat-label,
// .mat-form-field-label {
// color: rgba(0, 0, 0, 0.38) !important;
// }
// .mat-select-arrow,
// .mat-select-arrow svg {
// color: rgba(0, 0, 0, 0.38) !important;
// fill: rgba(0, 0, 0, 0.38) !important;
// }
// .mdc-notched-outline__leading,
// .mdc-notched-outline__notch,
// .mdc-notched-outline__trailing,
// .mat-form-field-outline {
// border-color: rgba(0, 0, 0, 0.12) !important;
// }
// }
Copy link

Choose a reason for hiding this comment

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

The disabled form field styles are being commented out in both light and dark themes. If these styles aren't being replaced elsewhere, this could cause accessibility issues as users may not be able to visually distinguish between enabled and disabled form fields. Consider either keeping these styles or providing alternative styling for disabled fields.


ngOnInit(): void {
this.organizationForm.get('timeZoneName')?.disable();
// this.organizationForm.get('timeZoneName')?.disable();
Copy link

Choose a reason for hiding this comment

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

Uncommenting this line makes the 'timeZoneName' field directly editable by users, which could lead to inconsistencies with the 'timezone' field. The component has logic that updates 'timezone' based on 'timeZoneName' changes, but not vice versa. If users can directly edit 'timeZoneName', they might enter values that don't correspond to any valid timezone offset.

Consider either:

  1. Keeping the field disabled as it was before
  2. Adding validation to ensure 'timeZoneName' always corresponds to a valid timezone
  3. Implementing two-way synchronization between 'timezone' and 'timeZoneName'

@Chandan-walker Chandan-walker merged commit 2b3fe37 into development Feb 23, 2026
1 check failed
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.

2 participants