"Modulus" Medical System #34

New issue

Open

opened 2026-04-18 22:33:53 +00:00 by Isaac-Scout-Proto · 1 comment

Isaac-Scout-Proto commented

2026-04-18 22:33:53 +00:00

(Migrated from github.com)

Plan and create the following:

A design document for this task. (I will add the link to the design doc here when I create the document and write the outline for the task within it)
A medical system to replace the current system in place.
Alter the medical code base (I don't know the proper term for it as of posting this task) so that changes to the medical system in place do not require changes for all code items that depend on the medical code base.

Plan and create the following: - A design document for this task. (I will add the link to the design doc here when I create the document and write the outline for the task within it) - A medical system to replace the current system in place. - Alter the medical code base (I don't know the proper term for it as of posting this task) so that changes to the medical system in place do not require changes for all code items that depend on the medical code base.

LukeZurg22 commented

2026-04-18 23:30:14 +00:00

(Migrated from github.com)

This is a vague.

"Alter the whole medical part of the codebase so that changes to the medical system don't require changes for all code items depending on the codebase."

If you update a YAML prototype directly, or any components with any fields, then you have to update all the yml files referencing them.

"A medical system to replace the current system."

Just any medical system? What's wrong with the current one? I quite like it; why go through the effort of upheaving the entire system on the basis of zero flaws?

"A design document for this task."

Comprehensive documentation for the task of creating a new medical system is fun. Rather than link an external document, you could include the tasks involved in it unless it's multiple pages long.

This is a vague. > "Alter the whole medical part of the codebase so that changes to the medical system don't require changes for all code items depending on the codebase." If you update a YAML prototype directly, or any components with any fields, then you **have** to update all the yml files referencing them. > "A medical system to replace the current system." Just any medical system? What's wrong with the current one? I quite like it; why go through the effort of upheaving the entire system on the basis of zero flaws? > "A design document for this task." Comprehensive documentation for the task of creating a new medical system is fun. Rather than link an external document, you could include the tasks involved in it unless it's multiple pages long.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Byrd-Station/Byrd#34

No description provided.

Rows
Columns