feat(core): implements fields max length service

[Blue-B-code]

#Thank you for your contribution to openIMIS!
#Please complete the sections below. Anything in comments is guidance and can be deleted.

Description

In Openimis, several backend models enforce maximum field lengths (max_length). Consequently, when the frontend sends a payload with fields exceeding these limits, the backend returns an error message for the mutation. To prevent users from encountering this—given that the backend error message is not particularly user-friendly—we implemented a service that blocks further input once the max_length is reached and displays a message to inform the user (see screenshot).

The implemented approach is as follows:

On the backend, a new type is added to the queries: MaxLengthConstraintsGQLType

Expected payload:

query GetMaxLengthConstraints { maxLengthConstraints { constraints } }

which returns something like:

{ "data": { "maxLengthConstraints": { "insuree": { "uuid": 36, "chfId": 50, "lastName": 100, "otherNames": 100, "marital": 1, "passport": 25, "phone": 50, "email": 100, "currentAddress": 200, "geolocation": 250, "status": 2 } } } }

On the frontend, this payload is retrieved, and component properties are used to identify the max_length for the current field and manage user interaction.

Type of Change

• Feature
• Bug fix
• Chore (Refactor, Docs, CI/CD)
• Enhancement

Related Issue(s) / Task(s)

• Requires feat(core): implements fields max length service openimis-be-core_py#431
• Relates to [link to github PR], this needs to be merged before [link to github PR]
• External reference (e.g., Jira):

Demo

Upload screenshots/gifs or link to any demo video here.

Checklist

• Unit tests added/modified
• I18n / translation handled

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud