Skip to content

Conversation

@gnehapk
Copy link
Contributor

@gnehapk gnehapk commented Jun 25, 2019

After implementing, the IPI modal looks like -

ipi-modal

@spadgett @vojtechszocs This is the initial PR of OCS operator workflow for IPI. Please review.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 25, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gnehapk
To complete the pull request process, please assign cloudbehl
You can assign the PR to them by writing /assign @cloudbehl in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link
Contributor

Hi @gnehapk. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 25, 2019
>
<ModalTitle>Create OCS Service</ModalTitle>
<ModalBody>
3 new nodes and a AWS bucket will be created in order to create the OCS Service.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd suggest handling this via some message prop instead of using a hard-coded text 😃


export const ipiDeployementModal = createModalLauncher<ipiModalProps>(IPIDeployementModal);

export type ipiModalProps = {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please use <ComponentName>Props, i.e. this should be IPIDeployementModalProps.

} from '@console/internal/components/utils/promise-component';

class IPIDeployementModal extends PromiseComponent<ipiModalProps, PromiseComponentState> {
state = {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please mark the state as readonly and use the appropriate type.

readonly state: IPIDeployementModalState = ...

PromiseComponentState,
} from '@console/internal/components/utils/promise-component';

class IPIDeployementModal extends PromiseComponent<ipiModalProps, PromiseComponentState> {
Copy link
Contributor

Choose a reason for hiding this comment

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

The PromiseComponentState type is currently used only in promise-component.spec.tsx.

I think that each modal component should explicitly declare its own state type, i.e. please add this after the props type:

type IPIDeployementModalState = {
  inProgress: boolean;
  errorMessage: string;
};

@spadgett spadgett added this to the v4.2 milestone Jun 26, 2019
@gnehapk
Copy link
Contributor Author

gnehapk commented Jul 10, 2019

Sent out a new PR after the new design changes. Hence, closing this PR

@gnehapk gnehapk closed this Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants