Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Farajaland form updates #805

Merged
merged 9 commits into from
Feb 15, 2024
Merged

Farajaland form updates #805

merged 9 commits into from
Feb 15, 2024

Conversation

getIDType(
'birth',
'informant',
hideIfNidIntegrationEnabled.concat(detailsExist),
Copy link
Collaborator

Choose a reason for hiding this comment

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

detailsExist doesn't apply to informant so we need hideIfInformantMotherOrFather instead

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good catch @Zangetsu101 I am going to correct that

return {
name: fieldName,
required,
custom: true,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need this field to be a custom one? If not then as it's a default field that we support, we need to add it as a valid optional field here: https://github.com/opencrvs/opencrvs-core/blob/develop/packages/config/src/handlers/forms/validation.ts#L228

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks @Zangetsu101, I don't think it needs to be a custom one, but rather an optional field. I am on it

Comment on lines 60 to 63
spouseDetailsExistConditionals*/,
spouseDetailsExistConditionals,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we clean up the imports here a bit please?

Comment on lines 73 to 75
spouseNameInEnglish*/,
spouseNameInEnglish
Copy link
Collaborator

Choose a reason for hiding this comment

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

Similarly here

src/form/death/index.ts Show resolved Hide resolved
@euanmillar
Copy link
Collaborator

Euan to discuss if this should be cherry-picked on top of 1.3.3

@Zangetsu101
Copy link
Collaborator

@tahmidrahman-dsi Apologies as I don't think we can make the id fields non-custom (i.e. optional fields) as this would restrict us on the types of field we can support, so let's revert that change I requested previously

@euanmillar
Copy link
Collaborator

@tahmidrahman-dsi we have decided to put this into 1.3.3. Can you make a new PR based on the release-v1.3.3 branch and cherry-pick these commits onto it and re-submit this PR please?

@tahmidrahman-dsi tahmidrahman-dsi changed the base branch from develop to release-v1.3.3 February 13, 2024 09:53
src/client-config.js Outdated Show resolved Hide resolved
@Zangetsu101 Zangetsu101 merged commit cee7df0 into release-v1.3.3 Feb 15, 2024
1 check passed
@Zangetsu101 Zangetsu101 deleted the ocrvs-6202-6203-6204 branch February 15, 2024 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants