[Fixes #203] Resolve Patient DOB Bug #205
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #203.
As described in the issue, the date of birth field was not persisting values correctly when navigating between sections. This was happening because:
TextInput
, whereas before it was using aDateInput
DateInput
was being used, the DOB value from the server was converted into adate
object to be compatible with the format expected with this input field (i.e.new Date(dateOfBirth)
) but this is no longer necessaryTherefore, to resolve this issue the DOB value when populating the form with the DOB data from the server has to be kept as a
string
rather than converting it into adate
object.Some additional key changes:
DateInput
but are no longer valid forTextInput
to resolve console warningsen-CA
to match the format that HTML date input expects. However iOS Safari doesn't support themax
attribute as seen from many online discussions like this oneScreenRecording_02-20-2025.22-02-18_1.MP4