Changes

addchild usecase added

CHANGES relatd to adding child

CHANGES relatd to adding child

user-signup-e2e

crash fix

added clearstate

added teardown

Gender commented

corrected

https://github.com/UstadMobile/Respect/issues/57
fixed

account list not scrollable fixed

Added mandatory field test

~/StudioProjects/RespectTest/respect-server/log - will getignore

fix for issue 76

test tag added

commented mandatory field tests

Added hideKeyboard command

Added teacher flow test

update test

duplicate string remove

updated test flow - single test

updated to password*

merged with main

updated to date of birth field

Gender and DOB manadatory field tests

DOB can't be future date - test added

DOB updated test

changes in SignupViewModel.kt

updated student name and flow change

changes in SignupViewModel.kt

changes in SignupViewModel.kt

changes AddChildAccountUseCase.kt

commented DownloadIntegrationTest.kt as it contain error

feat: Validate date of birth on save

This commit introduces validation to prevent the date of birth from being in the future. The validation is now handled in the `PersonEditViewModel` when the save button is clicked, rather than restricting the date selection in the UI.

Key changes:
- Removed the future date restriction from the `RespectLocalDateField` date picker, allowing users to select any date.
- Added a new string resource `date_of_birth_in_future` for the error message.
- Updated `PersonEditViewModel` to validate the date of birth upon saving. If the selected date is in the future, an error message is displayed and the save is aborted.
- Modified `PersonEditScreen` to display the date of birth validation error message below the input field.

refactor: Improve `fullName` generation in `PersonExt`

This commit refactors the `fullName` extension function for the `Person` model to more robustly handle whitespace and optional name parts.

The function now trims leading/trailing whitespace from `givenName`, `middleName`, and `familyName`. It also ensures that spaces are only added between name parts if the preceding part is not empty, preventing extra spaces in the final output.

feat: Clear email error on change

This commit clears the email validation error message in the `PersonEditViewModel` when the user modifies the email address. The phone number error handling already had similar logic, and this change makes the email field consistent.

commit

If Using family name it is duplicating the other family name and middle name so changed to given name

Restore deleted Maestro flow test not related to this branch

Restore deleted Maestro flow file 004_create_report_test.yaml

feat: Enhance ClazzDetailScreen with more information

This commit updates the class details screen to provide more comprehensive information about the class and its pending members.

Key changes:
- Displays the class description in the `TopAppBar`.
- Shows a count of pending teacher and student requests in the "Pending requests" section header.
- For pending teachers and students, the list now shows their role (teacher or student), gender, and date of birth.
- In the class edit screen, the `*` indicating a required field has been removed from the "Class Name" label to simplify the UI.

Updated test flow

Updated setDate.js file

updated to main

updated mandatory field error

string change

string change

string change

Updated test

refactor: Use fullName for person display and internationalize labels

This commit updates the `ClazzDetailScreen` to use the `person.fullName()` extension function for displaying user names, ensuring a consistent format. It also replaces hardcoded text labels for "Gender" and "DOB" with internationalized string resources.

chore: Fix Kotlin linting issues

This commit addresses several Kotlin linting errors by removing unnecessary whitespace. The changes include:
- Removing space before `else` keywords.
- Fixing spacing around commas.
- Removing space before `if` conditions.

feat: Make email optional for persons

This commit updates the validation and display logic to correctly handle cases where a person's email is not provided.

feat: Add validation for first and last name

This commit introduces validation to ensure that the first and last name fields are not blank when editing a person's details.

Make ResultDest its own class so that it can support two types of return destinations: KClass based and route based.

feat: Add validation for first and last name

This commit introduces validation to ensure that the first and last name fields are not blank when editing a person's details.

Updated mandatory test

style: Standardize test function naming

This commit updates the test function names in `ValidateEmailUseCaseTest.kt` to follow the camelCase convention, removing backticks and descriptive phrases.

Update AssignmentEditViewModel to use route based result destination.

Add navigation return result support for selecting a person.

refactor: Standardize required field validation message

This commit replaces the generic `required` string resource with a more specific `required_field` resource for consistency in validation error messages.

Key changes:
- In `PersonEditViewModel`, the validation logic for first name, last name, and gender now uses `Res.string.required_field`.
- The `PersonEditScreen` and `RespectGenderExposedDropDownMenuField` have been updated to display the specific validation error message from the view model state, falling back to a default required text.
- The gender dropdown component now accepts and displays a `UiText` error message, improving how validation feedback is presented to the user on both the Person Edit and Sign Up screens.

refactor: Use UiText for class name validation

This commit updates the class name validation to use `UiText` instead of a plain `String`. This allows for more flexible and localized error messages.

Key changes:
- `ClazzEditUiState.clazzNameError` is now of type `UiText?`.
- The `ClazzEditViewModel` now sets `clazzNameError` to a `UiText` from string resources.
- `ClazzEditScreen` has been updated to use `uiTextStringResource` to display the localized validation message.
- The resource string for the class name label was changed from `class_name` to `name` for consistency.

chore: Format code for consistency

This commit applies minor code formatting changes to improve consistency across the codebase. Specifically, it adjusts spacing around operators and in conditional statements.

Put invite code on PersonList and remove AddPersonToClazz .

Fix select person from list. Initial implementation of adding to class.

Fix EnrollmentEntity for database

EnrollmentEntity did not store the full uid string of the related class and person, it was relying on a join to the class and person entity. This fails when attempting to create a pending enrollment for a student who profile which is being created as part of a parental registration (on the client).

Update PersonListScreen to make it easier for the Maestro test to get the invite code.

Minor tidy changes:
1) Remove personedit padding on column - each field has its own padding
2) Remove "dob" as a string - this is short, but not clear.

updated copy-paste - invite code

Remove class_name_label string and change admin_add_app_and_teacher to use name not class name.

updated erase text flow

updated "Pending requests.*"

updated ".*Pending requests.*"

Fix labels on 001_001 invite test to match those currently used
Ensure edit screens have testTags on textfields.

updated to text

Fix label match admin_add_app_and_teacher

Pending requests had the number of requests added to the end, so previous assertvisible failed. Users have role added in brackets.

updated eraseText

Fix lesson selection flow to use RouteResultDest

test

test updated

test updated

Attempt to fix intermittent ConcurrentModificationException on server.

Koin DI factories can be called concurrently when multiple requests are ongoing. Add ReentrantLock when creating and linking account scope on the server.

test added