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
Add a new flow for create sample application #6038
Conversation
724c132
to
d0d0896
Compare
/retest |
d0d0896
to
148c012
Compare
This looks good to me! |
@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 |
148c012
to
19313ce
Compare
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. |
19313ce
to
e22c7af
Compare
/retest |
1 similar comment
/retest |
frontend/packages/dev-console/src/components/import/ImportSamplePage.tsx
Outdated
Show resolved
Hide resolved
Get Started using applications by choosing a code sample. | ||
</div> | ||
</div> | ||
<div className="odc-empty-state__content"> |
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.
How come we are using empty-state styles here?
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.
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.
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'd prefer that these were made into a reusable component or into a shared style file.
e22c7af
to
e19a596
Compare
/retest |
Get Started using applications by choosing a code sample. | ||
</div> | ||
</div> | ||
<div className="odc-empty-state__content"> |
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'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'], |
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.
Why the intermediate segments is
and isNs
? Seems unnecessary as you're not going to clash with any other route.
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.
Do you mean I should have the route like /samples/:ns/:is/:isNs
?
459c85a
to
72a482a
Compare
72a482a
to
34eff7a
Compare
34eff7a
to
f99b5da
Compare
/lgtm |
[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 |
/retest |
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
Browser conformance: