-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MDS-5431] create new or historical record from one window - in New Flow #2713
[MDS-5431] create new or historical record from one window - in New Flow #2713
Conversation
…create-new-or-historical-record-from-one-window
services/core-web/src/components/Forms/ExplosivesPermit/ExplosivesPermitForm.tsx
Outdated
Show resolved
Hide resolved
services/core-web/src/components/Forms/ExplosivesPermit/ExplosivesPermitFormNew.tsx
Outdated
Show resolved
Hide resolved
return ( | ||
isFeatureEnabled(Feature.ONE_WINDOW_FOR_CREATING_NEW_OR_HISTORICAL_ESUP) && parentView ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While it doesn't hurt anything to have this included here as well as the ExplosivesPermitFormNew
, Once it's live we'll eventually be deleting this file (and renaming the new one to this name), so it won't provide much benefit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Only thing is, with this both changes (5353 & 5431) can be controlled using two different flags.
WDYT? Removing this and controlled both features through one flag is better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I lean towards a single flag since it's all part of the same feature that will be released as a whole.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applied the changes needed for this. Please verify.
… records (#2715) * adding soft deletion of now_application_document_identity_xref * adding soft delete in now_submissions document table * adding document.deleted_ind check for false in now_app * filtering out now_submission docs with deleted_ind equal true * adding deleted_ind check to submission_documents secondary join * removing space change * removing space change * removing space change
remove update on issue date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌🏻
…d functionality (#2714) * Refactor Explosives Permit Form for better readability and functionality The code refactor has mainly focused on the `MagazineFormNew.tsx` and `ExplosivesPermitFormNew.tsx` components. Unnecessary `Form.Item` wrappers have been removed, resulting in cleaner code and more readable form fields. Ability to remember and set active panel for the Collapse element in the MagazineForm has been added which will enhance user experience as users will no longer lose their panel selections after a page reload. In the `ExplosivesPermitFormNew.tsx`, the form name has been made more descriptive and specific (EXPLOSIVES_PERMIT_NEW). Also, removed unused 'bindActionCreators and change' import to enhance performance. All these changes were made based on PR review comments. * made delete button clickable * fixed a couple of file errors * remove broken validation * restored Tara's work
* switched compare function to moment from native Date so that 2023-02-15 does not become 2023-02-14 at 6pm local time * [MDS-5337] Use artifactory to cache fontawesome pacakges * Updated yarn.lock * Fixed react type errors --------- Co-authored-by: Tara Epp <[email protected]>
…cated (#2717) * [MDS-5337] Use artifactory to cache fontawesome pacakges * Updated yarn.lock * Fixed react type errors * MDS-5537 Unset old fontawesome token config
…w' of https://github.com/bcgov/mds into mds-5431-create-new-or-historical-record-from-one-window
68cc32e
Create a separate PR for this. #2720 |
Objective
MDS-5431
Why are you making this change? Provide a short explanation and/or screenshots
This is part of the PR-2708. With this change the same flow is enabled in the new flow (when the
esup_permit_amendment
feature is enabled).