-
Notifications
You must be signed in to change notification settings - Fork 73
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
[2.11] Embed New Backend form into a modal #2413
Conversation
Is the idea to use this modal everywhere where a user can create a new backend or just here where creating the backend is like a side step in the process of adding a backend to a product? |
@thomasmaas the idea here is to help a user in the process of selecting a Backend by giving them the option to create a new one without leaving the context. So yes, we will still have a dedicated page featuring the Backend creation form for when a user chooses the traditional creation path (eg. from the Dashboard or the Backends index page) |
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.
UX looks good to me!
@josemigallas any chance you could add |
Do you mean change the current button's |
@thomasmaas thank you for spotting this! @josemigallas the naming rule for those ids can be found in this issue THREESCALE-6729 I think we should actually track two buttons in this page:
Question: will displaying the modal dialog change the URL of the page? |
No it won't. One thing to point out is that the same form is going to be used in its own page, meaning the same |
It's not. In pendo we can still get the specific numbers for both usages by scoping the click on that button to different page urls. And in case of this modal the scoping page url would be the 'add backend to product' page url. |
- remove console.log - fixes colorbox selector
4e30dbc
to
67254b9
Compare
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.
LGTM (js side)
|
||
const VALIDATION_CONSTRAINTS = { | ||
name: { length: { minimum: 1 } }, | ||
privateEndpoint: { url: { schemes: ['http', 'https', 'ws', 'wss'] } } |
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 think this explains https://issues.redhat.com/browse/THREESCALE-7480 @josemigallas
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.
What this PR does / why we need it:
Replaces the link to the Backend's
new
page with a button that displays a modal containing the form. Once a backend is created it will be selected in the dropdown.Which issue(s) this PR fixes