Backend data type definition & Frontend user input data UI

[dusixian]

Backend data type definition & Frontend user input data UI

♻️ Current situation & Problem

The project requires backend data structures to store manually entered health data and a corresponding frontend UI for users to input these values. This PR introduces data models and a input interface for manual health data entry.

⚙️ Release Notes

Backend Data Type Definitions:

• Heart Rate (HeartRateEntry) – measured in BPM.
• Temperature (TemperatureEntry) – stored in Celsius or Fahrenheit with unit handling.
• Oxygen Saturation (OxygenSaturationEntry) – percentage validation included.
• Blood Pressure (BloodPressureEntry) – systolic & diastolic values with validation.
• Lab Results (LabEntry) – categorized using LabTestType enum.
• Implemented isValidDate() function to ensure data timestamps are not set in the future.

Frontend UI for Manual Data Entry:

1. DataInputForm View:
   • Displays an input form based on the selected health data type.
   • Includes date & time pickers for accurate timestamping.
   • Supports multiple field types (text fields, number inputs, pickers).
   • Dynamically validates input to ensure correct data entry.
2. AddData View:
   • Displays 6 data categories for user to choose.

📚 Documentation

Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.

✅ Testing

Unit Tests Ensured numeric validation for all manual entry fields (e.g., temperature, blood pressure). Confirmed correct data structure initialization with sample values.

📝 Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• I agree to follow the Code of Conduct and Contributing Guidelines.

[codecov]

Codecov Report

Attention: Patch coverage is 11.41141% with 295 lines in your changes missing coverage. Please review.

Project coverage is 62.67%. Comparing base (26edeff) to head (65cc57f).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
NeutroFeverGuard/DataInputForm.swift	0.00%	230 Missing ⚠️
NeutroFeverGuard/AddDataView.swift	0.00%	41 Missing ⚠️
NeutroFeverGuard/HelperFunc.swift	0.00%	14 Missing ⚠️
NeutroFeverGuard/DataError.swift	0.00%	10 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main       #5       +/-   ##
===========================================
- Coverage   86.75%   62.67%   -24.07%     
===========================================
  Files          21       26        +5     
  Lines         709     1042      +333     
===========================================
+ Hits          615      653       +38     
- Misses         94      389      +295     

Files with missing lines	Coverage Δ
NeutroFeverGuard/DataType.swift	100.00% <100.00%> (ø)
NeutroFeverGuard/DataError.swift	0.00% <0.00%> (ø)
NeutroFeverGuard/HelperFunc.swift	0.00% <0.00%> (ø)
NeutroFeverGuard/AddDataView.swift	0.00% <0.00%> (ø)
NeutroFeverGuard/DataInputForm.swift	0.00% <0.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 26edeff...65cc57f. Read the comment docs.

[PSchmiedmayer]

@dusixian As noted in https://github.com/orgs/CS342/discussions/113#discussioncomment-12051489, ensure that you update all dependencies to the latest version in Xcode and committing all the updated project files + Package.resolved file. You need to run File -> Swift Packages -> Update to Latest Package Versions in Xcode. This might fix your current testing errors.

[mmervecerit]

Hi @dusixian,

I reviewed your PR, here is my feedback:

• Your changes in eventview and scheduleview should be reverted i believe, since those lines were added by Paul to the original template to fix issues, and i added them in my previous PR.
  -Also the units of lab tests are important to know, and critical to input/show in UI. (hemoglobin for example, it is g/dL and WBC is usually cells per microliter) This might be good to talk with @viraj28m when he is implementing FHIR records of the lab values and have unit conversions if required.

[dusixian]

@mmervecerit Hi Merve! Thanks for your advice. I've changed the eventview and scheduleview following your commits. And for the unit of lab variables, I changed the frontend so the current UI shows the unit when user entry the lab values.

[mmervecerit]

@dusixian these were the changes are from the main template Paul pushed, so we should keep them?