ManifestForm Front end Validation

[dpgraham4401]

Break down the (e-)Manifest form into components (already started), each component should have accompanying validation (see below)

These dependencies are already available in Haztrak

• react-hook-form
• yup schema validation
• These can also be easily integrated with react-bootstrap form components for styling/accessibility.

client side validation is handled with yup, react-hook-form has some basic validation built it, currently we're keeping that logic in yup validation schema. The entire manifest form can be broken down in to reusable components (e.g., address validation/form for all handlers should be the same).

• Address validation schema #111
  • note: TSD and transporter info should generally match what's in RCRAInfo (for hazardous waste manifest), since this is an example application we should keep it so that information is pulled from RCRAInfo whenever available
• #110
  • lots of work that can be done here
• Manifest Form: General info #109
  • basic stuff, like potential ship date should be greater than current date

Field specific front end validation

• Created Date field validation #441
  • This Field is Managed by RCRAInfo. It should never be input from the haztrak user, as such, it's 'optional' (null/undefined when a draft manifest is created in haztrak).
• Status field Validation #439
  • This field is partially managed by RCRAInfo. Once the Manifest is created in RCRAinfo, it should only ever by read only (not editable). When the manifest is just in draft phase (only a draft in haztrak, not yet created in RCRAInfo) then users should be able to select whether it's still in draft status. Validation for many other fields depends on the status of this field.
• Submission Type field validation #443
  • The two choices (for the scope of this project) should only be 'electronic' or 'Hybrid'. If Electronic is selected, we need to add a feature that will allow users to search for a registered generator (several features away).
• Shipped Date Field Validation #440
  • This field is managed by RCRAInfo like createdDate, and UpdatedDate.
• Emergency Phone form field #456
• Manifest must have a valid generator validation #466
• Manifest must have at least 1 wasteline validation #467
• Manifest must have at least 1 transporter validation #468
• Manifest must have a valid designated facility validation #469

Wasteline

• #491
• If "EPA Waste"true, federal waste required #496
• container number is required and greater than 0 #492
• container type is required #493
• quantity is required and greater than 0 #494
• quantity UOM is required #495

[dpgraham4401]

marking this issue as closed as we have successfully been able to sufficiently validate the manifest entered by the user to create electronic manifests in RCRAInfo