Skip to content

Refactor collection form page for better composition#3744

Merged
dvail merged 2 commits intomasterfrom
dv/collection-form-structural-refactor
Nov 10, 2022
Merged

Refactor collection form page for better composition#3744
dvail merged 2 commits intomasterfrom
dv/collection-form-structural-refactor

Conversation

@dvail
Copy link
Contributor

@dvail dvail commented Nov 8, 2022

Description (1 of 3)

This is the first of three PRs that aims to restructure the Collection form page to achieve two goals:

  1. Allow better composition of components, so that the collection form can be used in places other than the form page (e.g. in a modal)
  2. Decouple the validation of the incoming collection data from the rendering of the results

These PRs aim to result in no functional changes and are only a restructuring to allow more flexibility for upcoming requirements.

The first goal is accomplished with the following changes:

  • Remove the showBreadcrumbs boolean prop and allow passing the full header contents from the parent container to the CollectionForm. This allows us to customize, or omit, any content that appears above the form inputs. This is needed for the in-page modal as well as the modal in the VulnMgmt reporting page.
  • Move the action callback handlers (edit/clone/save/delete) from the CollectionForm to the parent CollectionFormPage. This allows us to decouple the editing of the data in the form from what happens when the data changes. e.g. The collection page and the modals will have different behavior.

The second goal is accomplished with the following changes:

  • Extract the form itself from the PatternFly Drawer. This allow us to better handle the contents of the DrawerContents and the DrawerPanel. This is done in a follow up PR to attempt to preserve history as much as possible.
  • Perform the parsing of the back end collection response at the Drawer level, instead of at the CollectionFormPage level. This allows us to display an error in place of the form if the UI cannot handle the response, while still allowing us to render the CollectionResults. This is needed because although the UI can only handle a subset of the collection rules, it would still be possible (and useful) to still display the results for that collection.

Rough visual overview

This chart shows the flow of data and the conditional rendering before this change.

  • The form actions were performed inside the CollectionForm component
  • The entirety of the rendering of the CollectionForm was handled by the component itself
  • The conditional rendering for unsupported collection responses was performed in the CollectionFormPage component, rendering either the entire form contents and results, or nothing at all.
flowchart LR
    id2-->id3
    id4-->id7-->id8
    subgraph CollectionFormPage.tsx
        id1(request collection from server)-->id2(parse collection)
        id3{is collection valid?}
        id3-->id3-y((Yes))   
        id3-->id3-n((No))   
        id3-n-->id6(render error information)    
        style id6 fill:#f99 
        id3-y-->id5
        subgraph CollectionForm.tsx
            subgraph Drawer Content
                id3-y-->id4(render form)       
                style id4 fill:#9f9 
                id7(Header, Breadcrumbs)
                id8(Form)
            end
            subgraph Drawer Panel
                id5(render collection results)
                style id5 fill:#9f9 
            end
            id8-->|on form action|id9
            id9(Handle Actions)-->id10(on submit, generate server response)
            id9-->id11(on action: handle edit, clone, delete)
        end
    end
Loading

This chart shows the flow of data and the conditional rendering after this change.

  • The form actions are now performed as callbacks inside the parent CollectionFormPage component
  • The rendering of the header contents of the CollectionForm is handled by the parent component
  • The conditional rendering for unsupported collection responses s performed in the CollectionForm component, allowing us to render the form and the collection results independently of a parsing error.
flowchart LR
    subgraph CollectionFormPage.tsx
        id1(request collection from server)
        id2(pass header JSX as prop)
        id8-->|on form action|id10
        id10(Handle Actions)-->id12(on submit, generate server response)
        id10-->id11(on action: handle edit, clone, delete)
        id1-->id2
        id1-->id3
        id2-.->id7
        subgraph CollectionFormDrawer.tsx
            id3(Render Form Drawer)
            id3-->id4
            id3-->|Unsupported collections can still render results|id5
            subgraph Drawer Panel
                id5(render collection results)
                style id5 fill:#9f9 
            end
            subgraph Drawer Content
                subgraph CollectionForm.tsx
                    id7(render passed header prop)
                    id8(Form)
                end
                id4-->id4-y((Yes))   
                id4{is collection valid?}
                id4-y-->id9(render form)       
                style id9 fill:#9f9 
                id9-->id7
                id9-->id8
                id4-->id4-n((No))   
                id4-n-->id6(render error information)    
                style id6 fill:#f99 
            end
        end
    end
Loading

This chart shows the plans in a future PR to render a collection form in a modal, independent of the parent container. In this case the parent is the CollectionFormPage, but in the future this can be a separate page that renders the modal (e.g. the VulnMgmt reporting page).

flowchart TB
    subgraph CollectionFormPage.tsx
        id1(request collection from server)
        id2(pass header JSX as prop)
        id3-->|on form action|id10
        id10(Handle Form Actions)
        id1-->id2
        id1-->id3
        id2-.->id3
        subgraph CollectionFormDrawer.tsx
            id3(Render Form and Results)
            id3b(On collection link click)-->idb1
        end
    end

    idb1(Open modal with another collection)
    idb1-->ida1

    subgraph CollectionFormModal.tsx
        ida1(request collection from server)
        ida2(pass header JSX as prop)
        ida1-->ida2
        ida1-->ida3
        ida2-.->ida3
        subgraph CollectionFormDrawer
            ida11(On collection link click)-->ida10(Links open new tab)
            ida3(Render Form and Results)
        end
    end
Loading

Checklist

  • Investigated and inspected CI test results
  • Unit test and regression tests added
  • Evaluated and added CHANGELOG entry if required
  • Determined and documented upgrade steps
  • Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.

Testing Performed

Manual testing of all form functionality:

  • Create, edit, clone and delete. (Both from the collections table and from the actions menu within the form page)
  • Add name selectors
  • Add label selectors
  • Empty selector validation
  • Ability to show/hide results panel
  • Results panel behavior responds to smaller screen sizes

@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2022

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ghost
Copy link

ghost commented Nov 9, 2022

Images are ready for the commit at edf0795.

To use with deploy scripts, first export MAIN_IMAGE_TAG=3.72.x-565-gedf079596e.

@dvail dvail requested review from bradr5 and pedrottimark November 9, 2022 17:09
};

const defaultCollectionData: Collection = {
const defaultCollectionData: Omit<CollectionResponse, 'id'> = {
Copy link
Contributor

@pedrottimark pedrottimark Nov 9, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You keep teaching me more TypeScript.

For my understanding, what are pro and con versus id: '' property?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main benefit is that this is explicitly saying we don't care that the CollectionResponse object is missing the id property (and in fact this forbids it from happening). Setting an empty value of id: '' would allow mixing of objects in the code that either have a valid id or have an empty string. To prevent bugs when we wanted to access the id we would need to add if (id === '') {} runtime checks, while using Omit enforces this at compile time.

pageAction={validPageActionProp}
/>
<>
<PageSection className="pf-u-h-100" padding={{ default: 'noPadding' }}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comparing to CollectionsTablePage below brings to mind a question: what is the reason to factor PageSection element out of CollectionsFormPage?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Admittedly this is probably a detail lost in the shuffle. I agree it makes more sense to be in CollectionFormPage to match the usage of CollectionsTablePage.

Copy link
Contributor

@pedrottimark pedrottimark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for breaking the refactor into steps with clear explanation. 2 questions.

@dvail
Copy link
Contributor Author

dvail commented Nov 9, 2022

/retest

@dvail dvail merged commit ab05bfc into master Nov 10, 2022
@dvail dvail deleted the dv/collection-form-structural-refactor branch November 10, 2022 18:52
vikin91 added a commit that referenced this pull request Nov 25, 2022
7ffc6be ROX-13368: Skip failing nongroovy tests on PG (#3721)
bbdd7a0 Bump github.com/gofrs/uuid from 4.3.0+incompatible to 4.3.1+incompatible (#3642)
1f253f2 Bump github.com/google/certificate-transparency-go from 1.1.3 to 1.1.4 (#3543)
d434c8d [ROX-13030] : Add delete collection API endpoint and service implementation (#3648)
f062c21 Dashrews/ROX-13253 wait for central-db to come back after bounce and allow FATAL connection lost error (#3537)
edc1174 CI: Fill the gaps for https://testgrid.k8s.io/ (#3715)
86d7c54 ROX-13231: use passed context when non-postgres (#3540)
9093195 Add less specific type for BE collection response string (#3728)
5abb652 Only enable ROX_OBJECT_COLLECTIONS feature flag during gke-postgres-ui-e2e job (#3727)
4f64cd1 Add centralDBOnly mode in render (#3707)
d67bbe5 Dashrews/ROX-13082 UUID searcher and common updates to set allow use of postgres UUID PR 1 of 4 (#3679)
6f829d5 ROX-13259: graphInit called during init time (#3705)
f3bc50d ROX-13380: Conditional rendering edges for deployments and namespaces (#3641)
3764476 ROX-12319: implement smoke test step with groovy test filter (#3220)
f202fd4 ROX-11826: Disable kernel support package uploads for managed central (#3661)
61f03dc ROX-11101: Remove deprecated resources from central (#3115)
e6aa6d7 ROX-11101: Restore Role permission in UI (#3428)
3203e04 ROX-11101: Remove deprecated resources (#3036)
a35f41e Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#3733)
4120524 Bump snakeyaml from 1.29 to 1.33 in /qa-tests-backend (#3732)
e1785c0 Bump github.com/coreos/go-systemd/v22 from 22.4.0 to 22.5.0 (#3724)
870df4a Bump google.golang.org/api from 0.101.0 to 0.102.0 (#3723)
721454c Generalize User-Agent setup (#3672)
6a11bf0 Bumps collector version to 3.11.x-145-gc345f72f5e (#3736)
ec5d343 [ROX-12923] Walk retries - remainder work (#3729)
40f3d43 ROX-13440: Replace ambiguous central with sensor in networkGraph integration test (#3730)
281ed22 Bump groovy-xml from 2.5.18 to 2.5.19 in /qa-tests-backend (#3741)
49d1651 Bump github.com/prometheus/client_golang from 1.13.1 to 1.14.0 (#3742)
b5544aa Bump cloud.google.com/go/storage from 1.27.0 to 1.28.0 (#3743)
9c61e53 ensure CVSS is present for istio vulns (#3706)
ae29d52 ROX-13452: don't always clobber scoped ctx when non-postgres (#3748)
517bf05 ROX-13261: DryRunUpdate on collection datastore (#3687)
baf7654 ROX-13378: Group new resources with deprecated in UI (#3690)
569922f ROX-13421: Enable roxctl netpol generate and add tech-preview messages (#3740)
2465fc5 Dashrews/ROX-13082 UUID generator templates PR 2 of 4 (#3681)
c093c68 Bump slack-api-client from 1.20.2 to 1.27.0 in /qa-tests-backend (#3752)
2c860bb Bump ubi8-micro from 8.6 to 8.7 in /operator (#3751)
80eb04c Make deploy.sh and deploy-local.sh pass shellcheck (#3582)
2182b43 Dashrews/ROX-13082 UUID test updates PR 3 of 4 (#3694)
6dc6ca5 [ROX-13403] : Fix node -> topVuln sub resolver bug when node cves is empty (#3689)
1b21361 Move integration tests for page title from general to specific containers (#3675)
e1a9f31 Bump google.golang.org/api from 0.102.0 to 0.103.0 (#3773)
a05ea31 Bump golang.org/x/crypto from 0.1.0 to 0.2.0 (#3772)
65ddf4f ROX-12824: Add roxctl commands to generate Central DB bundle (#3602)
c3f1e2f Remove obsolete authProviders request for Integrations page (#3759)
7ccd54d Dashrews/ROX-13082 UUID protos generated PR 4 of 4 (#3698)
9ab5c8f cleanup image digest utilities (#3764)
187ed44 ROX-11931: Convert junit failure artifacts to Slack attachments (#3438)
b5d8790 ROX-13432: leaning up unused code copied/pasted from topology demo (#3750)
ab05bfc Refactor collection form page for better composition (#3744)
c5562f7 Remove babel devDependencies in ui-components (#3761)
2b90b3a Extract collection form from drawer wrapper layout (#3745)
a779fc9 [ROX-12625 + ROX-13032] : Add GetCollectionCount and UpdateCollection endpoints and  services (#3749)
e77f0da Upgrade cypress 11.0.0 devDependencies in ui (#3760)
a3fba94 ROX-13068: Use real data for deployment details (#3688)
4c7d90e ROX-12617: Collection to search query converter (#3683)
3e98aec ROX-13067: fill out port configurations section of deployment details (#3714)
a48de36 ROX-12835: Add support for NodeScanV2 to Sensor (#3533)
30c5dc7 ROX-13466: Fix deletion of groups with empty properties (#3756)
5cb2470 Add autocomplete for name selector dropdowns (#3676)
b9a75ad ROX-13464 adding flows dropdown in NG (#3763)
3217a67 [ROX-13500] Perform type check for V1 CronJob (#3787)
af3790d Remove bulk delete from collections table (#3776)
dda123b Add more info in migration log (#3788)
179f0c9 ROX-13502: Remove the circular dependency between cluster datastore init and cscc notifier init (#3790)
029d584 Update SCANNER_VERSION (#3774)
cbca57c Bump github.com/ckaznocha/protoc-gen-lint from 0.2.4 to 0.3.0 (#3783)
3613b56 Bump golang.org/x/tools from 0.2.0 to 0.3.0 (#3782)
5fc0a6a Bump github.com/google/go-containerregistry from 0.12.0 to 0.12.1 (#3781)
1d1c687 Bump controller-gen version to 0.10.0 (#3754)
c3a5290 Untie documentation link from the product version (#3799)
ed822aa use correct package for migration (#3784)
397a0b4 Validate that label keys are valid k8s labels and ensure correct key splitting (#3777)
edd1050 Rename variable ScannerGRPCEndpoint to ScannerSlimGRPCEndpoint (#3657)
6662c9f ROX-13378: Access Control page permissions (#3720)
b0e73c5 fix Operator reconciliation for external Central DB (#3796)
b83bc1f ROX-13505: Fix error log scanning the postgres stat collection (#3795)
ca660cb Prevent the collection being edited from displaying in its own embedded list (#3778)
3f7b3fc [ROX-13441][POSTGRES] Propagate context correctly in retries (#3793)
e0cbc6f ROX-12839: Update changelog to announce removal of in-product docs (#3805)
696e8bc [ROX-12358] Follow up on vulnerability request proto change (#2851)
c4b46d8 Change getCollectionCount endpoint and updateCollection request type
5f2efbc remove make proto-fmt (#3804)
0c75540 Remove os.Std* from roxctl/central (#3758)
25a90de Add ability to view embedded collections in a pop up modal (#3747)
5c1bf81 ROX-13240: fix scanner-slim updates when WebSockets are used (#3704)
1d98577 Add more context to jira notifier logging (#3812)
da2fd28 ROX-13031: DryRun Collection API (#3766)
1c418d5 Test data migration code in postgres tests (#3803)
ed95b37 Update UI Collection requests for BE compatibiltiy (#3762)
09cc188 ROX-11931: Fix junit-parse install in CI (#3811)
d2b01e3 ROX-12814: Disable PolicyFieldsTest on openshift. (#3797)
d10ce27 ROX-13345: disable 'missing required registry' aspect on openshift (#3798)
3d22396 Update collector to 3.12 (#3809)
1eb33fb ROX-13347: Modify scope queries to included quoted cluster and nameace names, to allow exact matches instead of erroneous and unintended prefix matches. (#3767)
3811a69 ROX-12621: list collection selectors api (#3806)
f6d3f9d Add migration for groups with invalid values (#3789)
cc21125 Bugfixes for collection autocomplete (#3816)
7623dec ROX-9350 Use fine-grained host paths for compliance mounts (#2479)
b4bf5c2 Fix collector volumeMounts  (#3826)
0e9be05 ROX-12953: figure out last 4 versions of sensor automatically (#3611)
459c7ae ROX-12814: Add proper todo for reenabling the test (#3817)
9ee40ff ROX-13523: add isEnabled enum to central db spec (#3815)
535bc72 Replace requestConfig with routeMatcherMap in helper functions for integration tests (#3686)
2b75b61 `gosec` G104: Add `ShouldErr(err)` that returns `err` (#3830)
fb1b82f WIP: Introduce nodescan call
35f8a8f WIP: Prepare converter
716144b Moved and renamed fake nodescan tests
4748de7 Introduce real node scanner with conversion functions
5e6d9a8 wip: real scanner
0169868 wip: log results
1438d2c wip: Debug Analyze call
b09894c wip: Debug Analyze call
3ceed72 wip: Update and improve debug logs
d1669fd Remove copied lib, bump scanner version, add debug
14a3f73 Merge branch 'master' into mm/ROX-12967-real-nodescan
fbd0450 Fix style issues
17ccb31 Debug: let both scans finish to see what they return
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants