You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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
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).
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.
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).
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
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
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).
Field specific front end validation
Wasteline
The text was updated successfully, but these errors were encountered: