Skip to content
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

Add a new flow for create sample application #6038

Merged

Conversation

rohitkrai03
Copy link
Contributor

Fixes: https://issues.redhat.com/browse/ODC-4091

Analysis / Root cause:
There's no quick way for users to create applications out of samples provided by openshift right now.

Solution Description:
Add a new import flow for creating samples quickly.

Screen shots / Gifs for design review:
cc: @openshift/team-devconsole-ux @beaumorley @serenamarie125
Sample Flow

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

@openshift-ci-robot openshift-ci-robot added the component/dev-console Related to dev-console label Jul 20, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 20, 2020
@rohitkrai03
Copy link
Contributor Author

/retest

@bkrikori
Copy link

This looks good to me!

@debsmita1
Copy link
Contributor

@rohitkrai03 Just a question, do you think we should have the namespace bar with applications dropdown in the Sample app form? I am asking this because suppose in the topology user is in the context of app x & then tries to create a sample app. The user will expect the workload to be grouped under app x. Have a look at the gif below
sample-app

@rohitkrai03
Copy link
Contributor Author

@rohitkrai03 Just a question, do you think we should have the namespace bar with applications dropdown in the Sample app form? I am asking this because suppose in the topology user is in the context of app x & then tries to create a sample app. The user will expect the workload to be grouped under app x. Have a look at the gif below
sample-app

Ohh, I already had a conversation around this with PM and UX. Just forgot to update the code. Removed the application selector from both the pages.

@rohitkrai03
Copy link
Contributor Author

/retest

1 similar comment
@rohitkrai03
Copy link
Contributor Author

/retest

Get Started using applications by choosing a code sample.
</div>
</div>
<div className="odc-empty-state__content">
Copy link
Contributor

Choose a reason for hiding this comment

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

How come we are using empty-state styles here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, it's the same exact style that we needed for this page as well as it looks exactly same as EmptyState. So I just re-used it directly.

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 prefer that these were made into a reusable component or into a shared style file.

@rohitkrai03
Copy link
Contributor Author

/retest

Get Started using applications by choosing a code sample.
</div>
</div>
<div className="odc-empty-state__content">
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 prefer that these were made into a reusable component or into a shared style file.

type: 'Page/Route',
properties: {
exact: true,
path: ['/samples/ns/:ns/is/:is/isNs/:isNs'],
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the intermediate segments is and isNs? Seems unnecessary as you're not going to clash with any other route.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do you mean I should have the route like /samples/:ns/:is/:isNs?

@openshift-ci-robot openshift-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. component/shared Related to console-shared and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 22, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2020
@rohitkrai03
Copy link
Contributor Author

Updated screens -

Screenshot from 2020-07-23 04-42-12
Screenshot from 2020-07-23 04-42-17

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 23, 2020
@christianvogt
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, rohitkrai03

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

The pull request process is described here

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

@rohitkrai03
Copy link
Contributor Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit c466a9c into openshift:master Jul 24, 2020
@spadgett spadgett added this to the v4.6 milestone Jul 28, 2020
@rohitkrai03 rohitkrai03 deleted the create-sample-flow branch July 24, 2021 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/dev-console Related to dev-console component/shared Related to console-shared lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants