If a header field is defined, clicking it will collapse all sections up to the next header.

https://developer.chrome.com/devtools/docs/console-api

State has moved to Visit parent container

And make the Date type actually have a date, as well

For the sake of coding additional fields in the future, Field JSX classes should be consistent in implementation of properties such as componentWillMount and componentWillReceiveProps.

• Add setValue function to handle transition between different states
• setValue should determine validity based on passed props object
• Move console.* functions to after initial variable declarations in each function
• Variable declarations with undefined values should proceed those with defined values.
• Reorganize method in this order: getInitialState, componentWillMount, componentWillReceiveProps, setValue, onXChange, [other functions], render
• getInitialState should return value as an empty string instead of null when the field is empty (unless otherwise required by the component)
• State values like status, display, and displayState should be condensed to one or two consistently-utilized terms
• Use block comments for information instead of //

Columns should have new comments when modified, but Schema creator doesn't seem to want to change them if the column already exists

• Adding a field without a name and then importing data breaks the system
• Add confirmation modal before overwriting fields
• "Mode" option - overwrite or append?

FlowEditor blocks all type changes for multiselect inputs, but select should be an option

Currently, the summaryFields object is simply divided in half and rendered as two columns. Would be nice to organize cards by their headers.

• Prevent submission of patient without a name?
• Disable if File inputs have pending uploads

Follow visit from one stage to another after submission

FORCEPT needs to run on all devices without crippling lag. React modules must be optimized to increase speed.

Todo:

• Reduce/eliminate usage of console.log
• Locally store any variable used more than once
• Find a faster alternative to Object.keys
• Clean-up HTML (try to reduce DOM size)
• Find other ways to optimize code
• Run benchmarks

Possible ways to increase performance

• Render each patient's DOM as the viewport scrolls down to reduce ridiculously large DOM size

Because a Visit ID has to be made first

Recreate:

• Create a patient, give them a photo
• Check them out
• Import the patient (photo shows)
• Check them out again
• Import the patient again (photo is broken)

Allow field numbers and column data to be imported via spreadsheet

If deleting fields does, deleting stages should as well