Skip to content

Fix to ensure age can be saved even if estimated birthdate is set#132

Closed
nnpvaan wants to merge 1 commit into
senaite:masterfrom
nnpvaan:fix-age-requires-estimated-birthdate
Closed

Fix to ensure age can be saved even if estimated birthdate is set#132
nnpvaan wants to merge 1 commit into
senaite:masterfrom
nnpvaan:fix-age-requires-estimated-birthdate

Conversation

@nnpvaan
Copy link
Copy Markdown
Contributor

@nnpvaan nnpvaan commented Nov 4, 2025

Description of the issue/feature this PR addresses

Fix issue where age is saved even when estimated_birthdate is set.

Current behavior before PR

In some cases, the age field is set before the estimated_birthdate is assigned.
This causes the age value to be stored even though no estimated_birthdate exists, leading to inconsistent data.

Desired behavior after PR is merged

Automatically mark estimated_birthdate as True when age is set, ensuring that the age field is always stored correctly

--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.

@nnpvaan nnpvaan force-pushed the fix-age-requires-estimated-birthdate branch from f16dc93 to c0eabfe Compare November 4, 2025 05:45
@nnpvaan nnpvaan changed the title Fix prevent setting age if it is set Fix to ensure age can be saved even if estimated birthdate is set Nov 4, 2025
@nnpvaan nnpvaan closed this Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant