[jira] [Updated] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-9339:
-
Description:
I think there some changes due for {{form-field-size}} component:
1. [~pkonstantinov] expressed his confusion multiple times about the fact that
{{form-field-size}} converts visible value when user changes scale. He suggests
to keep the view value the same and only scale the model value.
2. It wasn't the case at the moment {{form-field-size}} was added, but now some
form fields use different default scale (i.e. it's bytes vs megabytes).
[~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
figure out a better component API for cases like this.
3. Add autofocus support.
4. Fix validation error icon position:
!screenshot-1.png!
was:
I think there some changes due for {{form-field-size}} component:
1. [~pkonstantinov] expressed his confusion multiple times about the fact that
{{form-field-size}} converts visible value when user changes scale. He suggests
to keep the view value the same and only scale the model value.
2. It wasn't the case at the moment {{form-field-size}} was added, but now some
form fields use different default scale (i.e. it's bytes vs megabytes).
[~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
figure out a better component API for cases like this.
3. Add autofocus support.
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
> 4. Fix validation error icon position:
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-9339:
-
Attachment: screenshot-1.png
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[ https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661704#comment-16661704 ] Ilya Borisov commented on IGNITE-9941: -- [~kuaw26] I've implemented all the frontend parts, but a portion of backend needs some changes too: when admin creates a user, backend should not switch session to the new user. > Web Console: Add option to disable self-registration on Web Console > --- > > Key: IGNITE-9941 > URL: https://issues.apache.org/jira/browse/IGNITE-9941 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > It will be useful to have ability to disable self registration on Web Console. > We can add a special option on backend and also add a button "Add user" on > "Admin panel" screen. > If "self registration" disabled on backend and user trying to register he > should receive error like "You need to ask for invite your Web Console > administrator". > Web Console administrator can create needed users and Web console will e-mail > notifications for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[ https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9941: Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web Console: Add option to disable self-registration on Web Console > --- > > Key: IGNITE-9941 > URL: https://issues.apache.org/jira/browse/IGNITE-9941 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > It will be useful to have ability to disable self registration on Web Console. > We can add a special option on backend and also add a button "Add user" on > "Admin panel" screen. > If "self registration" disabled on backend and user trying to register he > should receive error like "You need to ask for invite your Web Console > administrator". > Web Console administrator can create needed users and Web console will e-mail > notifications for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[ https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9941: Assignee: Ilya Borisov (was: Alexey Kuznetsov) > Web Console: Add option to disable self-registration on Web Console > --- > > Key: IGNITE-9941 > URL: https://issues.apache.org/jira/browse/IGNITE-9941 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > > It will be useful to have ability to disable self registration on Web Console. > We can add a special option on backend and also add a button "Add user" on > "Admin panel" screen. > If "self registration" disabled on backend and user trying to register he > should receive error like "You need to ask for invite your Web Console > administrator". > Web Console administrator can create needed users and Web console will e-mail > notifications for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[ https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661710#comment-16661710 ] Ilya Borisov commented on IGNITE-9941: -- [~pkonstantinov] what to test: 1. Signup page should behave exactly as before. 2. Email validation on signup page should work. 3. Admin page should have "Create user" link. 4. "Create user" dialog should create user. Admin doesn't get logged out after creating a user. > Web Console: Add option to disable self-registration on Web Console > --- > > Key: IGNITE-9941 > URL: https://issues.apache.org/jira/browse/IGNITE-9941 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > It will be useful to have ability to disable self registration on Web Console. > We can add a special option on backend and also add a button "Add user" on > "Admin panel" screen. > If "self registration" disabled on backend and user trying to register he > should receive error like "You need to ask for invite your Web Console > administrator". > Web Console administrator can create needed users and Web console will e-mail > notifications for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[ https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661710#comment-16661710 ] Ilya Borisov edited comment on IGNITE-9941 at 10/24/18 7:26 AM: [~pkonstantinov] what to test: 1. Signup page should behave exactly as before. 2. Email validation on signup page should work. 3. Admin page should have "Create user" link. 4. "Create user" dialog should create user. 5. Admin doesn't get logged out after creating a user. 6. New user is inserted into users list after successful user creation. 7. All fields on signup/user creation forms have validation. 8. Password, phone, checkbox input validation did not break in other places. was (Author: klaster_1): [~pkonstantinov] what to test: 1. Signup page should behave exactly as before. 2. Email validation on signup page should work. 3. Admin page should have "Create user" link. 4. "Create user" dialog should create user. Admin doesn't get logged out after creating a user. > Web Console: Add option to disable self-registration on Web Console > --- > > Key: IGNITE-9941 > URL: https://issues.apache.org/jira/browse/IGNITE-9941 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > It will be useful to have ability to disable self registration on Web Console. > We can add a special option on backend and also add a button "Add user" on > "Admin panel" screen. > If "self registration" disabled on backend and user trying to register he > should receive error like "You need to ask for invite your Web Console > administrator". > Web Console administrator can create needed users and Web console will e-mail > notifications for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[
https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661860#comment-16661860
]
Ilya Borisov commented on IGNITE-9941:
--
As a part of the task, email, password, checkbox and phone inputs were updated
to use `$input` validation approach instead of legacy `${form}[${name}]`.
> Web Console: Add option to disable self-registration on Web Console
> ---
>
> Key: IGNITE-9941
> URL: https://issues.apache.org/jira/browse/IGNITE-9941
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> It will be useful to have ability to disable self registration on Web Console.
> We can add a special option on backend and also add a button "Add user" on
> "Admin panel" screen.
> If "self registration" disabled on backend and user trying to register he
> should receive error like "You need to ask for invite your Web Console
> administrator".
> Web Console administrator can create needed users and Web console will e-mail
> notifications for them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[
https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661860#comment-16661860
]
Ilya Borisov edited comment on IGNITE-9941 at 10/24/18 7:28 AM:
As a part of the task email, password, checkbox and phone inputs were updated
to use _$input_ validation approach instead of legacy _${form}[${name}]_.
was (Author: klaster_1):
As a part of the task email, password, checkbox and phone inputs were updated
to use `$input` validation approach instead of legacy `${form}[${name}]`.
> Web Console: Add option to disable self-registration on Web Console
> ---
>
> Key: IGNITE-9941
> URL: https://issues.apache.org/jira/browse/IGNITE-9941
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> It will be useful to have ability to disable self registration on Web Console.
> We can add a special option on backend and also add a button "Add user" on
> "Admin panel" screen.
> If "self registration" disabled on backend and user trying to register he
> should receive error like "You need to ask for invite your Web Console
> administrator".
> Web Console administrator can create needed users and Web console will e-mail
> notifications for them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9941) Web Console: Add option to disable self-registration on Web Console
[
https://issues.apache.org/jira/browse/IGNITE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661860#comment-16661860
]
Ilya Borisov edited comment on IGNITE-9941 at 10/24/18 7:28 AM:
As a part of the task email, password, checkbox and phone inputs were updated
to use `$input` validation approach instead of legacy `${form}[${name}]`.
was (Author: klaster_1):
As a part of the task, email, password, checkbox and phone inputs were updated
to use `$input` validation approach instead of legacy `${form}[${name}]`.
> Web Console: Add option to disable self-registration on Web Console
> ---
>
> Key: IGNITE-9941
> URL: https://issues.apache.org/jira/browse/IGNITE-9941
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> It will be useful to have ability to disable self registration on Web Console.
> We can add a special option on backend and also add a button "Add user" on
> "Admin panel" screen.
> If "self registration" disabled on backend and user trying to register he
> should receive error like "You need to ask for invite your Web Console
> administrator".
> Web Console administrator can create needed users and Web console will e-mail
> notifications for them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6600) Web Console: Make a design of 403 and 404 pages
[ https://issues.apache.org/jira/browse/IGNITE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683437#comment-16683437 ] Ilya Borisov commented on IGNITE-6600: -- Looks good, [~kuaw26] you can do the rest. > Web Console: Make a design of 403 and 404 pages > --- > > Key: IGNITE-6600 > URL: https://issues.apache.org/jira/browse/IGNITE-6600 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Attachments: 403-page.png, 404-page.png > > Original Estimate: 8h > Time Spent: 9h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9799) Web console: remove unused code
Ilya Borisov created IGNITE-9799: Summary: Web console: remove unused code Key: IGNITE-9799 URL: https://issues.apache.org/jira/browse/IGNITE-9799 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Alexander Kalinin There's a bunch of legacy/unused code and dependencies, let's remove those. Here's an incomplete list, feel free to add more items: 1. angular-cookies dependency -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9820) Web console: unit test sourcemaps
Ilya Borisov created IGNITE-9820: Summary: Web console: unit test sourcemaps Key: IGNITE-9820 URL: https://issues.apache.org/jira/browse/IGNITE-9820 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Ilya Borisov Debugging unit tests without sourcemaps is cumbersome, so let's fix this. I've already tried [karma-sourcemap-loader|https://www.npmjs.com/package/karma-sourcemap-loader] and [this|https://stackoverflow.com/a/39175635/333777], but without success. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9569) Web console: use $inject for DI instead of arrays
[
https://issues.apache.org/jira/browse/IGNITE-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-9569:
Assignee: Alexey Kuznetsov (was: Ilya Borisov)
Broken unit test: fixed.
> Web console: use $inject for DI instead of arrays
> -
>
> Key: IGNITE-9569
> URL: https://issues.apache.org/jira/browse/IGNITE-9569
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> To do:
> 1. Remove provider registration by array spread, like this:
> {code:java}
> .service(...serviceArray){code}
> Instead, use the canonical AngularJS approach:
> {code:java}
> .service('SeriveName', Service){code}
> 2. Do not use array Di syntax for exported symbols:
> {code:java}
> export ['IgniteVersion', 'Confirm', function directive (version,
> confirm){}]{code}
> Instead, use $inject property:
> {code:java}
> export function directive(version, confirm) {}
> directive.$inject = ['IgniteVersion', 'Confirm']{code}
>
> Motivation:
> The changes above will make older providers accessible to TypeScript, which
> in turn will allow to increase type coverage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-9569) Web console: use $inject for DI instead of arrays
[
https://issues.apache.org/jira/browse/IGNITE-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reopened IGNITE-9569:
--
Assignee: Ilya Borisov (was: Pavel Konstantinov)
I missed a broken unit test, got to fix it.
> Web console: use $inject for DI instead of arrays
> -
>
> Key: IGNITE-9569
> URL: https://issues.apache.org/jira/browse/IGNITE-9569
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> To do:
> 1. Remove provider registration by array spread, like this:
> {code:java}
> .service(...serviceArray){code}
> Instead, use the canonical AngularJS approach:
> {code:java}
> .service('SeriveName', Service){code}
> 2. Do not use array Di syntax for exported symbols:
> {code:java}
> export ['IgniteVersion', 'Confirm', function directive (version,
> confirm){}]{code}
> Instead, use $inject property:
> {code:java}
> export function directive(version, confirm) {}
> directive.$inject = ['IgniteVersion', 'Confirm']{code}
>
> Motivation:
> The changes above will make older providers accessible to TypeScript, which
> in turn will allow to increase type coverage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9846) Web console: allow to $inject before function definition
Ilya Borisov created IGNITE-9846: Summary: Web console: allow to $inject before function definition Key: IGNITE-9846 URL: https://issues.apache.org/jira/browse/IGNITE-9846 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Andrey Novikov The issue: DI $inject property can't be set before function definition because of ESLint rules. This makes code harder to maintain and more error-prone. What to do: Loosen ESLint appropriate rules (probably no-use-before-define). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9846) Web console: allow to $inject before function definition
[ https://issues.apache.org/jira/browse/IGNITE-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-9846: - Description: The issue: DI $inject property can't be set before function definition because of ESLint rules. This makes code harder to maintain and more error-prone. What to do: Loosen ESLint appropriate rules (probably no-use-before-define). What to test afterwards: Nothing really, the changes are not application code related. was: The issue: DI $inject property can't be set before function definition because of ESLint rules. This makes code harder to maintain and more error-prone. What to do: Loosen ESLint appropriate rules (probably no-use-before-define). > Web console: allow to $inject before function definition > > > Key: IGNITE-9846 > URL: https://issues.apache.org/jira/browse/IGNITE-9846 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Andrey Novikov >Priority: Minor > > The issue: > DI $inject property can't be set before function definition because of > ESLint rules. This makes code harder to maintain and more error-prone. > What to do: > Loosen ESLint appropriate rules (probably no-use-before-define). > What to test afterwards: > Nothing really, the changes are not application code related. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9450) Web console: remove manual rendering from ignite-icon directive
Ilya Borisov created IGNITE-9450: Summary: Web console: remove manual rendering from ignite-icon directive Key: IGNITE-9450 URL: https://issues.apache.org/jira/browse/IGNITE-9450 Project: Ignite Issue Type: Improvement Reporter: Ilya Borisov Assignee: Ilya Borisov When making the ignite-icon directive, I had to manually render SVGs because at that moment we had to support IE11 and it doesn't support SVG directive template namespace. Since IE11 support has been dropped, we can safely use regular AngularJS template there and clean the code a bit. I think this change will also fix invisible icons in TestCafe E2E tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9569) Web console: use $inject for DI instead of arrays
[
https://issues.apache.org/jira/browse/IGNITE-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-9569:
Assignee: Alexey Kuznetsov (was: Ilya Borisov)
[~kuaw26] please review. I've also increased type coverage in places, partly as
an example of how to reference some Ignite service types.
> Web console: use $inject for DI instead of arrays
> -
>
> Key: IGNITE-9569
> URL: https://issues.apache.org/jira/browse/IGNITE-9569
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> To do:
> 1. Remove provider registration by array spread, like this:
> {code:java}
> .service(...serviceArray){code}
> Instead, use the canonical AngularJS approach:
> {code:java}
> .service('SeriveName', Service){code}
> 2. Do not use array Di syntax for exported symbols:
> {code:java}
> export ['IgniteVersion', 'Confirm', function directive (version,
> confirm){}]{code}
> Instead, use $inject property:
> {code:java}
> export function directive(version, confirm) {}
> directive.$inject = ['IgniteVersion', 'Confirm']{code}
>
> Motivation:
> The changes above will make older providers accessible to TypeScript, which
> in turn will allow to increase type coverage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625596#comment-16625596 ] Ilya Borisov commented on IGNITE-8245: -- [~kuaw26] can't reproduce in master: !screenshot-2.png! > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-8245: - Attachment: screenshot-2.png > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625596#comment-16625596 ] Ilya Borisov edited comment on IGNITE-8245 at 9/24/18 10:06 AM: [~kuaw26] failed to reproduce in master: !screenshot-2.png! was (Author: klaster_1): [~kuaw26] can't reproduce in master: !screenshot-2.png! > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-8245: Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9680) Web console: add component for status output
[ https://issues.apache.org/jira/browse/IGNITE-9680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-9680: - Description: Create a component that output status: 1. It should accept a list of possible statuses as an argument, each item should specify label to display, model value, color (red, green or regular) and whether to show an inline spinner or not. 2. It should also accept status value as an argument. 3. Given that same the status might be displayed in various places, provide a way to omit repeating lengthy statuses list argument. Maybe a component factory that binds statuses to a new component? 4. The new component should be based on either _ignite-status_ component or supersede it. Use the new component in: 1. Connected clusters dialog. was: Create a component that output status: 1. It should accept a list of possible statuses as an argument, each item should specify label to display, model value, color (red, green or regular) and whether to show an inline spinner or not. 2. It should also accept status value as an argument. 3. Given that same the status might be displayed in various places, provide a way to omit repeating lengthy statuses list argument. Maybe a component factory that binds statuses to a new component? Use the new component in: 1. Connected clusters dialog. Remove the _ignite-status_ component. > Web console: add component for status output > > > Key: IGNITE-9680 > URL: https://issues.apache.org/jira/browse/IGNITE-9680 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > > Create a component that output status: > 1. It should accept a list of possible statuses as an argument, each item > should specify label to display, model value, color (red, green or regular) > and whether to show an inline spinner or not. > 2. It should also accept status value as an argument. > 3. Given that same the status might be displayed in various places, provide a > way to omit repeating lengthy statuses list argument. Maybe a component > factory that binds statuses to a new component? > 4. The new component should be based on either _ignite-status_ component or > supersede it. > Use the new component in: > 1. Connected clusters dialog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9680) Web console: add component for status output
Ilya Borisov created IGNITE-9680: Summary: Web console: add component for status output Key: IGNITE-9680 URL: https://issues.apache.org/jira/browse/IGNITE-9680 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Ilya Borisov Create a component that output status: 1. It should accept a list of possible statuses as an argument, each item should specify label to display, model value, color (red, green or regular) and whether to show an inline spinner or not. 2. It should also accept status value as an argument. 3. Given that same the status might be displayed in various places, provide a way to omit repeating lengthy statuses list argument. Maybe a component factory that binds statuses to a new component? Use the new component in: 1. Connected clusters dialog. Remove the _ignite-status_ component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9552) Web console: add TypeScript support
[ https://issues.apache.org/jira/browse/IGNITE-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628306#comment-16628306 ] Ilya Borisov commented on IGNITE-9552: -- Added support for unit tests written in TS. > Web console: add TypeScript support > --- > > Key: IGNITE-9552 > URL: https://issues.apache.org/jira/browse/IGNITE-9552 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Original Estimate: 48h > Time Spent: 3.5h > Remaining Estimate: 13.75h > > What to do: > 1. ✔ Add TypeScript preset to babel config. > 2. ✔ Update webpack configs to load .ts files with babel-loader. > 3. ✔ Make sure eslint lint .ts files -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9680) Web console: add component for status output
[ https://issues.apache.org/jira/browse/IGNITE-9680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9680: Assignee: Alexander Kalinin (was: Ilya Borisov) [~alexdel] please review. > Web console: add component for status output > > > Key: IGNITE-9680 > URL: https://issues.apache.org/jira/browse/IGNITE-9680 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > > Create a component that output status: > 1. It should accept a list of possible statuses as an argument, each item > should specify label to display, model value, color (red, green or regular) > and whether to show an inline spinner or not. > 2. It should also accept status value as an argument. > 3. Given that same the status might be displayed in various places, provide a > way to omit repeating lengthy statuses list argument. Maybe a component > factory that binds statuses to a new component? > 4. The new component should be based on either _ignite-status_ component or > supersede it. > Use the new component in: > 1. Connected clusters dialog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10961) Web console: add more countries
Ilya Borisov created IGNITE-10961: - Summary: Web console: add more countries Key: IGNITE-10961 URL: https://issues.apache.org/jira/browse/IGNITE-10961 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Ilya Borisov Countries to add: * Taiwan * Hong Kong * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10961: - Assignee: Ilya Borisov (was: Alexey Kuznetsov) > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10961: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10961: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10965: -- Description: *The problem:* Some actions triggered by user might take awhile, during which user can click on action button multiple times and, depending on internal details, cause unwanted side effects (like registering multiple users instead of one). *Solution:* Disable action button when action is running. Tell user to wait that something is happening. This can be integrated into special button state. Places new button state can be used in: - User registration. I'd rather prefer that new button state would: - Not affect button dimensions because sudden button size change might look uncanny. Overlays are OK, though. This probably rules out spinning indicator inline with button label. - Not hide original button label so.user always knows what's in progress. - Work for all button styles. Unique background for each button type is not OK, same background or overlay is OK. This will simplify the implementation. The requirements above are not set in stone, every point is open for discussion. [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. was: *The problem:* Some actions triggered by user might take awhile, during which user can click on action button multiple times and, depending on internal details, cause unwanted side effects (like registering multiple users instead of one). *Solution:* Disable action button when action is running. Tell user to wait that something is happening. This can be integrated into special button state. Places new button state can be used in: - User registration. I'd rather prefer that new button state would: - Not affect button dimensions because sudden button size change might look uncanny. Overlays are OK, though. This probably rules out spinning indicator inline with button label. - Not hide original button label so.user always knows what's in progress. - Work for all button styles. Unique background for each button type is not OK, same background or overlay is OK. This will simplify the implementation. The requirements above are not set in stone, every point is open for discussion. [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Vica Abramova >Priority: Minor > Original Estimate: 8h > Remaining Estimate: 8h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10965) Web console: in progress state for buttons
[ https://issues.apache.org/jira/browse/IGNITE-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10965: -- Description: *The problem:* Some actions triggered by user might take awhile, during which user can click on action button multiple times and, depending on internal details, cause unwanted side effects (like registering multiple users instead of one). *Solution:* Disable action button when action is running. Tell user to wait that something is happening. This can be integrated into special button state. Places new button state can be used in: - User registration. I'd rather prefer that new button state would: - Not affect button dimensions because sudden button size change might look uncanny. Overlays are OK, though. This probably rules out spinning indicator inline with button label. - Not hide original button label so.user always knows what's in progress. - Work for all button styles. Unique background for each button type is not OK, same background or overlay is OK. This will simplify the implementation. The requirements above are not set in stone, every point is open for discussion. [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. was: *The problem:* Some actions triggered by user might take awhile, during which user can click on action button multiple times and, depending on internal details, cause unwanted side effects (like registering multiple users instead of one). *Solution:* Disable action button when action is running. Tell user to wait that something is happening. This can be integrated into special button state. Places new button state can be used in: - User registration. I'd rather prefer that new button state would: - Not affect button dimensions because sudden button size change might look uncanny. Overlays are OK, though. This probably rules out spinning indicator inline with button label. - Not hide original button label so.user always knows what's in progress. - Work for all button styles. Unique background for each button type is not OK, same background or overlay is OK. This will simplify the implementation. The requirements above are not set in stone, every point is open for discussion. [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. > Web console: in progress state for buttons > -- > > Key: IGNITE-10965 > URL: https://issues.apache.org/jira/browse/IGNITE-10965 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Vica Abramova >Priority: Minor > Original Estimate: 8h > Remaining Estimate: 8h > > *The problem:* > Some actions triggered by user might take awhile, during which user can > click on action button multiple times and, depending on internal details, > cause unwanted side effects (like registering multiple users instead of one). > *Solution:* > Disable action button when action is running. Tell user to wait that > something is happening. This can be integrated into special button state. > Places new button state can be used in: > - User registration. > I'd rather prefer that new button state would: > - Not affect button dimensions because sudden button size change might look > uncanny. Overlays are OK, though. This probably rules out spinning indicator > inline with button label. > - Not hide original button label so.user always knows what's in progress. > - Work for all button styles. Unique background for each button type is not > OK, same background or overlay is OK. This will simplify the implementation. > The requirements above are not set in stone, every point is open for > discussion. > [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10538) Make ignite-grid component for handling missing agent and cluster
[ https://issues.apache.org/jira/browse/IGNITE-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744837#comment-16744837 ] Ilya Borisov commented on IGNITE-10538: --- [~alexdel] looks good enough. I'm not sure about coupling the component with AgentManager service versus passing state value though binding, but it doesn't matter much in the end. > Make ignite-grid component for handling missing agent and cluster > - > > Key: IGNITE-10538 > URL: https://issues.apache.org/jira/browse/IGNITE-10538 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Alexander Kalinin >Priority: Major > > Currently we have such an aproach: When agent or cluster is not availibe we > block the whole screen and show a modal window with instructions (like in > Notebooks screen). This approach is a bad UX case as it frustrates user with > blocking and forcing to change state. > We should implement a less obtrusive aproach by showing message in body of > ignite-grid table, allowing user to stay on current state and not blocking > the whole UI. > This component should comply for following requirements: > 1) It sholuld be universal - applicable in context of any ignite-grid table > usage. > 2) Should handle common cases like missing agent or cluster under the hood. > 3) Should have a possibility of enhancing for other special cases in > different components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10538) Web console: make ignite-grid component for handling missing agent and cluster
[ https://issues.apache.org/jira/browse/IGNITE-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10538: -- Summary: Web console: make ignite-grid component for handling missing agent and cluster (was: Make ignite-grid component for handling missing agent and cluster) > Web console: make ignite-grid component for handling missing agent and cluster > -- > > Key: IGNITE-10538 > URL: https://issues.apache.org/jira/browse/IGNITE-10538 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Alexander Kalinin >Priority: Major > > Currently we have such an aproach: When agent or cluster is not availibe we > block the whole screen and show a modal window with instructions (like in > Notebooks screen). This approach is a bad UX case as it frustrates user with > blocking and forcing to change state. > We should implement a less obtrusive aproach by showing message in body of > ignite-grid table, allowing user to stay on current state and not blocking > the whole UI. > This component should comply for following requirements: > 1) It sholuld be universal - applicable in context of any ignite-grid table > usage. > 2) Should handle common cases like missing agent or cluster under the hood. > 3) Should have a possibility of enhancing for other special cases in > different components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10965) Web console: in progress state for buttons
Ilya Borisov created IGNITE-10965: - Summary: Web console: in progress state for buttons Key: IGNITE-10965 URL: https://issues.apache.org/jira/browse/IGNITE-10965 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Vica Abramova *The problem:* Some actions triggered by user might take awhile, during which user can click on action button multiple times and, depending on internal details, cause unwanted side effects (like registering multiple users instead of one). *Solution:* Disable action button when action is running. Tell user to wait that something is happening. This can be integrated into special button state. Places new button state can be used in: - User registration. I'd rather prefer that new button state would: - Not affect button dimensions because sudden button size change might look uncanny. Overlays are OK, though. This probably rules out spinning indicator inline with button label. - Not hide original button label so.user always knows what's in progress. - Work for all button styles. Unique background for each button type is not OK, same background or overlay is OK. This will simplify the implementation. The requirements above are not set in stone, every point is open for discussion. [~vabramova] to provide design, [~Klaster_1] or [~alexdel] to implement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10489) Web console: validation messages are shown twice in configuration
[ https://issues.apache.org/jira/browse/IGNITE-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10489: - Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web console: validation messages are shown twice in configuration > - > > Key: IGNITE-10489 > URL: https://issues.apache.org/jira/browse/IGNITE-10489 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.8 > > Attachments: image-2018-11-30-14-59-19-188.png > > Time Spent: 28m > Remaining Estimate: 0h > > What happens: > When validation is triggered for any form in configuration, _two_ validation > messages are shown simultaneously: one under the input and another in tooltip. > !image-2018-11-30-14-59-19-188.png! > What should happen: > Tooltip-style validation messages should not be visible on configuration > screens. > The issues is caused by IGNITE-9811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10489) Web console: validation messages are shown twice in configuration
[ https://issues.apache.org/jira/browse/IGNITE-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743665#comment-16743665 ] Ilya Borisov commented on IGNITE-10489: --- [~pkonstantinov] I've fixed a bug where horizontal error in form-field-size had incorrect position, please test again. > Web console: validation messages are shown twice in configuration > - > > Key: IGNITE-10489 > URL: https://issues.apache.org/jira/browse/IGNITE-10489 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.8 > > Attachments: image-2018-11-30-14-59-19-188.png > > Time Spent: 28m > Remaining Estimate: 0h > > What happens: > When validation is triggered for any form in configuration, _two_ validation > messages are shown simultaneously: one under the input and another in tooltip. > !image-2018-11-30-14-59-19-188.png! > What should happen: > Tooltip-style validation messages should not be visible on configuration > screens. > The issues is caused by IGNITE-9811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10890) Web console: UIRouter cleanup
[ https://issues.apache.org/jira/browse/IGNITE-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10890: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web console: UIRouter cleanup > - > > Key: IGNITE-10890 > URL: https://issues.apache.org/jira/browse/IGNITE-10890 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Labels: architecture, ui, wizard > Original Estimate: 6h > Time Spent: 2.5h > Remaining Estimate: 3.5h > > 1. Do not depend on _@uirouter/angularjs/lib/legacy/stateEvents_, replace all > legacy $scope events with transition-based API. > 2. Remove _@uirouter/visualizer_, which is only used for development. > The goal is to decrease bundle size and drop legacy APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10890) Web console: UIRouter cleanup
[ https://issues.apache.org/jira/browse/IGNITE-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743668#comment-16743668 ] Ilya Borisov commented on IGNITE-10890: --- [~alexdel] looks good, [~kuaw26] please merge. > Web console: UIRouter cleanup > - > > Key: IGNITE-10890 > URL: https://issues.apache.org/jira/browse/IGNITE-10890 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Labels: architecture, ui, wizard > Original Estimate: 6h > Time Spent: 2.5h > Remaining Estimate: 3.5h > > 1. Do not depend on _@uirouter/angularjs/lib/legacy/stateEvents_, replace all > legacy $scope events with transition-based API. > 2. Remove _@uirouter/visualizer_, which is only used for development. > The goal is to decrease bundle size and drop legacy APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749491#comment-16749491 ] Ilya Borisov commented on IGNITE-8420: -- [~alexdel] can you merge master in and sync the changes between branches? > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Ilya Borisov >Priority: Major > Original Estimate: 32h > Time Spent: 10h > Remaining Estimate: 22h > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-8420: Assignee: Alexander Kalinin (was: Ilya Borisov) > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Original Estimate: 32h > Time Spent: 10h > Remaining Estimate: 22h > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11034) Web console: update some dependencies
Ilya Borisov created IGNITE-11034: - Summary: Web console: update some dependencies Key: IGNITE-11034 URL: https://issues.apache.org/jira/browse/IGNITE-11034 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Alexander Kalinin We need to update: 1. AngularJS to latest 1.7 release (1.7.6) in order to support lazy module loading. 2. typescript-eslint-parser has been deprecated in a favor of it's fork, see details [here|https://eslint.org/blog/2019/01/future-typescript-eslint]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749480#comment-16749480 ] Ilya Borisov commented on IGNITE-10961: --- [~ysergeev] done. > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9879) Web console: split major features to modules - configuration
[
https://issues.apache.org/jira/browse/IGNITE-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-9879:
-
Remaining Estimate: 16h (was: 48h)
Original Estimate: 16h (was: 48h)
> Web console: split major features to modules - configuration
>
>
> Key: IGNITE-9879
> URL: https://issues.apache.org/jira/browse/IGNITE-9879
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Original Estimate: 16h
> Remaining Estimate: 16h
>
> The issue:
> 1. _app.js_ is massive, hard to maintain and often a source of various merge
> conflicts.
> 2. Even if some code is de facto separated by feature
> (configuration/queries/admin/profile), no agreement was made on how to
> structure directories, which leads to confusion and app.js growth.
> I propose to:
> 1. Reorganize source code file structure:
> {noformat}
> frontend
> app
> configuration
> queries
> profile
> admin
> common
> {noformat}
> 2. Slim _app.js_ down to something like this:
> {noformat}
> import common from './common'
> import configuration from './configuration'
> import queries from './queries'
> import profile from './profile'
> import admin from './admin'
> export default angular.module('ignite-console', [
> common.name,
> configuration.name,
> queries.name,
> profile.name,
> admin.name
> ])
> {noformat}
> Each directory inside app will follow the same module structure as agreed
> upon before (i.e. components/services/filters, etc).
> 3. In order to test water, update the configuration module first and if
> everything goes as expect proceed with other modules.
> [~kuaw26], [~anovikov] what do you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9879) Web console: split major features to modules - configuration
[
https://issues.apache.org/jira/browse/IGNITE-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-9879:
-
Remaining Estimate: 48h
Original Estimate: 48h
> Web console: split major features to modules - configuration
>
>
> Key: IGNITE-9879
> URL: https://issues.apache.org/jira/browse/IGNITE-9879
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The issue:
> 1. _app.js_ is massive, hard to maintain and often a source of various merge
> conflicts.
> 2. Even if some code is de facto separated by feature
> (configuration/queries/admin/profile), no agreement was made on how to
> structure directories, which leads to confusion and app.js growth.
> I propose to:
> 1. Reorganize source code file structure:
> {noformat}
> frontend
> app
> configuration
> queries
> profile
> admin
> common
> {noformat}
> 2. Slim _app.js_ down to something like this:
> {noformat}
> import common from './common'
> import configuration from './configuration'
> import queries from './queries'
> import profile from './profile'
> import admin from './admin'
> export default angular.module('ignite-console', [
> common.name,
> configuration.name,
> queries.name,
> profile.name,
> admin.name
> ])
> {noformat}
> Each directory inside app will follow the same module structure as agreed
> upon before (i.e. components/services/filters, etc).
> 3. In order to test water, update the configuration module first and if
> everything goes as expect proceed with other modules.
> [~kuaw26], [~anovikov] what do you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749589#comment-16749589 ] Ilya Borisov edited comment on IGNITE-10961 at 1/23/19 7:12 AM: As per suggestion in PR, I've changed "Country" field label to "Country/Region" (signup page, user creation by admin, user profile). I've also fixed local e2e runner. [~kuaw26] please review. was (Author: klaster_1): As per suggestion in PR, I've change "Country" field label to "Country/Region" (signup page, user creation by admin, user profile). I've also fixed local e2e runner. [~kuaw26] please review. > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10961: - Assignee: Ilya Borisov (was: Alexey Kuznetsov) > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10961: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10961) Web console: add more countries
[ https://issues.apache.org/jira/browse/IGNITE-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749589#comment-16749589 ] Ilya Borisov commented on IGNITE-10961: --- As per suggestion in PR, I've change "Country" field label to "Country/Region" (signup page, user creation by admin, user profile). I've also fixed local e2e runner. [~kuaw26] please review. > Web console: add more countries > --- > > Key: IGNITE-10961 > URL: https://issues.apache.org/jira/browse/IGNITE-10961 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > Countries to add: > * Taiwan > * Hong Kong > * Singapore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719910#comment-16719910 ] Ilya Borisov commented on IGNITE-10239: --- [~pkonstantinov] can you test the branch while Andrey performs the review? > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 10h 55m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9839: Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10726) Web console: error in console after configuration import
[ https://issues.apache.org/jira/browse/IGNITE-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10726: -- Attachment: the error.png > Web console: error in console after configuration import > > > Key: IGNITE-10726 > URL: https://issues.apache.org/jira/browse/IGNITE-10726 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: the error.png > > Original Estimate: 6h > Remaining Estimate: 6h > > What happens: > AngularJS error is thrown when switching between configuration domain models. > How to reproduce: > 1. Start demo mode, launch web agent. > 2. Go to configuration and perform DB import once. > 3. Open the result configuration domain models section. > 4. Import from in place DB, choose to overwrite domain models. > 5. Switch between several domain models. > The issue does not persist after page reload, this looks like faulty caching. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10726) Web console: error in console after configuration import
[ https://issues.apache.org/jira/browse/IGNITE-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10726: -- Description: What happens: AngularJS error is thrown when switching between configuration domain models. !the error.png! How to reproduce: 1. Start demo mode, launch web agent. 2. Go to configuration and perform DB import once. 3. Open the result configuration domain models section. 4. Import from in place DB, choose to overwrite domain models. 5. Switch between several domain models. The issue does not persist after page reload, this looks like faulty caching. was: What happens: AngularJS error is thrown when switching between configuration domain models. How to reproduce: 1. Start demo mode, launch web agent. 2. Go to configuration and perform DB import once. 3. Open the result configuration domain models section. 4. Import from in place DB, choose to overwrite domain models. 5. Switch between several domain models. The issue does not persist after page reload, this looks like faulty caching. > Web console: error in console after configuration import > > > Key: IGNITE-10726 > URL: https://issues.apache.org/jira/browse/IGNITE-10726 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: the error.png > > Original Estimate: 6h > Remaining Estimate: 6h > > What happens: > AngularJS error is thrown when switching between configuration domain models. > !the error.png! > How to reproduce: > 1. Start demo mode, launch web agent. > 2. Go to configuration and perform DB import once. > 3. Open the result configuration domain models section. > 4. Import from in place DB, choose to overwrite domain models. > 5. Switch between several domain models. > The issue does not persist after page reload, this looks like faulty caching. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10726) Web console: error in console after configuration import
Ilya Borisov created IGNITE-10726: - Summary: Web console: error in console after configuration import Key: IGNITE-10726 URL: https://issues.apache.org/jira/browse/IGNITE-10726 Project: Ignite Issue Type: Bug Components: UI, wizards Reporter: Ilya Borisov Assignee: Vasiliy Sisko Attachments: the error.png What happens: AngularJS error is thrown when switching between configuration domain models. How to reproduce: 1. Start demo mode, launch web agent. 2. Go to configuration and perform DB import once. 3. Open the result configuration domain models section. 4. Import from in place DB, choose to overwrite domain models. 5. Switch between several domain models. The issue does not persist after page reload, this looks like faulty caching. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10726) Web console: error in console after configuration import
[ https://issues.apache.org/jira/browse/IGNITE-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10726: -- Description: *What happens:* AngularJS error is thrown when switching between configuration domain models. *How to reproduce:* 1. Start demo mode, launch web agent. 2. Go to configuration and perform DB import once. 3. Open the result configuration domain models section. 4. Import from in place DB, choose to overwrite domain models. 5. Switch between several domain models. The issue does not persist after page reload, this looks like faulty caching. was: What happens: AngularJS error is thrown when switching between configuration domain models. !the error.png! How to reproduce: 1. Start demo mode, launch web agent. 2. Go to configuration and perform DB import once. 3. Open the result configuration domain models section. 4. Import from in place DB, choose to overwrite domain models. 5. Switch between several domain models. The issue does not persist after page reload, this looks like faulty caching. > Web console: error in console after configuration import > > > Key: IGNITE-10726 > URL: https://issues.apache.org/jira/browse/IGNITE-10726 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Vasiliy Sisko >Priority: Minor > Attachments: the error.png > > Original Estimate: 6h > Remaining Estimate: 6h > > *What happens:* > AngularJS error is thrown when switching between configuration domain models. > *How to reproduce:* > 1. Start demo mode, launch web agent. > 2. Go to configuration and perform DB import once. > 3. Open the result configuration domain models section. > 4. Import from in place DB, choose to overwrite domain models. > 5. Switch between several domain models. > The issue does not persist after page reload, this looks like faulty caching. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723668#comment-16723668 ] Ilya Borisov commented on IGNITE-9839: -- master has been merged into the branch. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Andrey Novikov (was: Ilya Borisov) [~anovikov] please review. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password". Navigation links block in sidebar should scroll and indicate that some content is hidden when viewport height is low enough. (was: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password".) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Attachment: navigation links block scroll example.png > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716109#comment-16716109 ] Ilya Borisov commented on IGNITE-10239: --- Extra items to test: 1. All public pages markup should remain intact. 2. All navigation links should still work, that includes links outside of navigation sidebar. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Ignite Flags: (was: Docs Required) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Attachment: new design example.png > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password". (was: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads.) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Andrey Novikov (was: Ilya Borisov) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9.4h > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Ilya Borisov (was: Andrey Novikov) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9.4h > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721015#comment-16721015 ] Ilya Borisov commented on IGNITE-8245: -- [~pkonstantinov] can't reproduce. > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Andrey Novikov (was: Ilya Borisov) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 10h 55m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721026#comment-16721026 ] Ilya Borisov commented on IGNITE-10239: --- [~anovikov] all done. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 10h 55m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.
[ https://issues.apache.org/jira/browse/IGNITE-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-8245: Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web console: "Warning" icon is displayed above "secured key" icon. > -- > > Key: IGNITE-8245 > URL: https://issues.apache.org/jira/browse/IGNITE-8245 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > warning_icon.png > > > See attachment. Reproduced in Safari. > Make the actual input borderless, move the border to outer element, shrink > the input element when an error notification has to be shown. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10486) Web console: wrong custom validation messages priority
Ilya Borisov created IGNITE-10486: - Summary: Web console: wrong custom validation messages priority Key: IGNITE-10486 URL: https://issues.apache.org/jira/browse/IGNITE-10486 Project: Ignite Issue Type: Bug Components: wizards Reporter: Ilya Borisov Assignee: Alexander Kalinin What happens: After IGNITE-9946 custom validation messages no longer override default messages. What should happen: Custom validation messages should override default messages. Issues fixed by IGNITE-9946 should remain fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-9839: - Summary: Web Console: update to RxJS 6 (was: Web Console: Migrate to new API of RxJS) > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 5h 19m > Remaining Estimate: 0h > > We are using old and new API of RxJS. > Lets refactor all old usages to new API. > New API is more flexible, no more issues with "missing imports" and we will > be able to migrate to RxJS 6.x from 5.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9839: Assignee: Alexey Kuznetsov (was: Ilya Borisov) [~kuaw26] please review. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 5h 19m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-9839: - Description: Since RxJS 6 is required by latest version of Angular, we won't be able to proceed with UI framework migration without it. To do: update import paths, convert to pipe API. (was: We are using old and new API of RxJS. Lets refactor all old usages to new API. New API is more flexible, no more issues with "missing imports" and we will be able to migrate to RxJS 6.x from 5.x.) > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 5h 19m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10489) Web console: validation messages are shown twice in configuration
[ https://issues.apache.org/jira/browse/IGNITE-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10489: -- Description: What happens: When validation is triggered for any form in configuration, _two_ validation messages are shown simultaneously: one under the input and another in tooltip. !image-2018-11-30-14-59-19-188.png! What should happen: Tooltip-style validation messages should not be visible on configuration screens. The issues is caused by IGNITE-9811. was: What happens: When validation is triggered for any form in configuration, _two_ validation messages are shown simultaneously: one under the input and another in tooltip. !image-2018-11-30-14-59-19-188.png! What should happen: Tooltip-style validation messages should not be visible on configuration screens. > Web console: validation messages are shown twice in configuration > - > > Key: IGNITE-10489 > URL: https://issues.apache.org/jira/browse/IGNITE-10489 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: image-2018-11-30-14-59-19-188.png > > > What happens: > When validation is triggered for any form in configuration, _two_ validation > messages are shown simultaneously: one under the input and another in tooltip. > !image-2018-11-30-14-59-19-188.png! > What should happen: > Tooltip-style validation messages should not be visible on configuration > screens. > The issues is caused by IGNITE-9811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10489) Web console: validation messages are shown twice in configuration
[ https://issues.apache.org/jira/browse/IGNITE-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10489: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) [~kuaw26] please review. > Web console: validation messages are shown twice in configuration > - > > Key: IGNITE-10489 > URL: https://issues.apache.org/jira/browse/IGNITE-10489 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: image-2018-11-30-14-59-19-188.png > > > What happens: > When validation is triggered for any form in configuration, _two_ validation > messages are shown simultaneously: one under the input and another in tooltip. > !image-2018-11-30-14-59-19-188.png! > What should happen: > Tooltip-style validation messages should not be visible on configuration > screens. > The issues is caused by IGNITE-9811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10486) Web console: wrong custom validation messages priority
[ https://issues.apache.org/jira/browse/IGNITE-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10486: -- Ignite Flags: (was: Docs Required) > Web console: wrong custom validation messages priority > -- > > Key: IGNITE-10486 > URL: https://issues.apache.org/jira/browse/IGNITE-10486 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > > What happens: > After IGNITE-9946 custom validation messages no longer override default > messages. > What should happen: > Custom validation messages should override default messages. Issues fixed by > IGNITE-9946 should remain fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10489) Web console: validation messages are shown twice in configuration
Ilya Borisov created IGNITE-10489: - Summary: Web console: validation messages are shown twice in configuration Key: IGNITE-10489 URL: https://issues.apache.org/jira/browse/IGNITE-10489 Project: Ignite Issue Type: Bug Components: wizards Reporter: Ilya Borisov Assignee: Ilya Borisov Attachments: image-2018-11-30-14-59-19-188.png What happens: When validation is triggered for any form in configuration, _two_ validation messages are shown simultaneously: one under the input and another in tooltip. !image-2018-11-30-14-59-19-188.png! What should happen: Tooltip-style validation messages should not be visible on configuration screens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: Migrate to new API of RxJS
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9839: Assignee: Ilya Borisov (was: Alexander Kalinin) > Web Console: Migrate to new API of RxJS > --- > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 3h > Remaining Estimate: 0h > > We are using old and new API of RxJS. > Lets refactor all old usages to new API. > New API is more flexible, no more issues with "missing imports" and we will > be able to migrate to RxJS 6.x from 5.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10486) Web console: wrong custom validation messages priority
[ https://issues.apache.org/jira/browse/IGNITE-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10486: - Assignee: Ilya Borisov (was: Alexander Kalinin) > Web console: wrong custom validation messages priority > -- > > Key: IGNITE-10486 > URL: https://issues.apache.org/jira/browse/IGNITE-10486 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > > What happens: > After IGNITE-9946 custom validation messages no longer override default > messages. > What should happen: > Custom validation messages should override default messages. Issues fixed by > IGNITE-9946 should remain fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10486) Web console: wrong custom validation messages priority
[ https://issues.apache.org/jira/browse/IGNITE-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10486: -- Description: What happens: After IGNITE-9946 custom validation messages no longer override default messages. What should happen: Custom validation messages should override default messages. Issues fixed by IGNITE-9946 should remain fixed. The issues is caused by IGNITE-9811. was: What happens: After IGNITE-9946 custom validation messages no longer override default messages. What should happen: Custom validation messages should override default messages. Issues fixed by IGNITE-9946 should remain fixed. > Web console: wrong custom validation messages priority > -- > > Key: IGNITE-10486 > URL: https://issues.apache.org/jira/browse/IGNITE-10486 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > > What happens: > After IGNITE-9946 custom validation messages no longer override default > messages. > What should happen: > Custom validation messages should override default messages. Issues fixed by > IGNITE-9946 should remain fixed. > The issues is caused by IGNITE-9811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10486) Web console: wrong custom validation messages priority
[ https://issues.apache.org/jira/browse/IGNITE-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10486: -- Description: What happens: After IGNITE-9946 custom validation messages no longer override default messages. What should happen: Custom validation messages should override default messages. Issues fixed by IGNITE-9946 should remain fixed. was: What happens: After IGNITE-9946 custom validation messages no longer override default messages. What should happen: Custom validation messages should override default messages. Issues fixed by IGNITE-9946 should remain fixed. The issues is caused by IGNITE-9811. > Web console: wrong custom validation messages priority > -- > > Key: IGNITE-10486 > URL: https://issues.apache.org/jira/browse/IGNITE-10486 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > > What happens: > After IGNITE-9946 custom validation messages no longer override default > messages. > What should happen: > Custom validation messages should override default messages. Issues fixed by > IGNITE-9946 should remain fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10318) Web console: use newer panels in query notebook screen
[ https://issues.apache.org/jira/browse/IGNITE-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10318: -- Attachment: screenshot-1.png > Web console: use newer panels in query notebook screen > -- > > Key: IGNITE-10318 > URL: https://issues.apache.org/jira/browse/IGNITE-10318 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: How query notebook screen look now.png, screenshot-1.png > > Original Estimate: 72h > Remaining Estimate: 72h > > "Queries notebook" screen is the last place where older style of collapsible > panels has remain in use. > What to do: > 1. Replace panels on "queries notebook" screen with panel-collapsible > component. > 2. Update query rename feature to use "Rename" button and new name prompt > instead on inline form. > 3. Move query remove button to context menu in panel actions. > 4. Move "Execute", "Execute on selected node", "Explain" and "Scan" button to > panel actions. All actions, except for "Execute" and "Scan", should be in > context menu. > 5. Remove legacy code used in older style collapsible panels. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10318) Web console: use newer panels in query notebook screen
[ https://issues.apache.org/jira/browse/IGNITE-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10318: - Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) > Web console: use newer panels in query notebook screen > -- > > Key: IGNITE-10318 > URL: https://issues.apache.org/jira/browse/IGNITE-10318 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: How query notebook screen look now.png, screenshot-1.png > > Original Estimate: 72h > Remaining Estimate: 72h > > "Queries notebook" screen is the last place where older style of collapsible > panels has remain in use. > What to do: > 1. Replace panels on "queries notebook" screen with panel-collapsible > component. > 2. Update query rename feature to use "Rename" button and new name prompt > instead on inline form. > 3. Move query remove button to context menu in panel actions. > 4. Move "Execute", "Execute on selected node", "Explain" and "Scan" button to > panel actions. All actions, except for "Execute" and "Scan", should be in > context menu. > 5. Remove legacy code used in older style collapsible panels. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10318) Web console: use newer panels in query notebook screen
[ https://issues.apache.org/jira/browse/IGNITE-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702997#comment-16702997 ] Ilya Borisov commented on IGNITE-10318: --- [~pkonstantinov] I've restored query action buttons under edit area, what do you think now? !screenshot-1.png! > Web console: use newer panels in query notebook screen > -- > > Key: IGNITE-10318 > URL: https://issues.apache.org/jira/browse/IGNITE-10318 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: How query notebook screen look now.png, screenshot-1.png > > Original Estimate: 72h > Remaining Estimate: 72h > > "Queries notebook" screen is the last place where older style of collapsible > panels has remain in use. > What to do: > 1. Replace panels on "queries notebook" screen with panel-collapsible > component. > 2. Update query rename feature to use "Rename" button and new name prompt > instead on inline form. > 3. Move query remove button to context menu in panel actions. > 4. Move "Execute", "Execute on selected node", "Explain" and "Scan" button to > panel actions. All actions, except for "Execute" and "Scan", should be in > context menu. > 5. Remove legacy code used in older style collapsible panels. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Ilya Borisov > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9839: Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709571#comment-16709571 ] Ilya Borisov edited comment on IGNITE-9839 at 12/5/18 3:30 AM: --- [~kuaw26] it affects most of the screens. was (Author: klaster_1): [~kuaw26] it affects all screens. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709571#comment-16709571 ] Ilya Borisov commented on IGNITE-9839: -- [~kuaw26] it affects all screens. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-9339:
Assignee: Andrey Novikov (was: Ilya Borisov)
[~anovikov] please review and merge.
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
> 4. Fix validation error icon position:
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9811) Web Console: Do not block "Save" button in case some inputs are invalid
[ https://issues.apache.org/jira/browse/IGNITE-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9811: Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web Console: Do not block "Save" button in case some inputs are invalid > --- > > Key: IGNITE-9811 > URL: https://issues.apache.org/jira/browse/IGNITE-9811 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > Let's not block "Save" button in case some inputs invalid. > In modern UI trends it is better to set focus to invalid filed and show > tooltip with error when user clicked on "Save" button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9811) Web Console: Do not block "Save" button in case some inputs are invalid
[ https://issues.apache.org/jira/browse/IGNITE-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692779#comment-16692779 ] Ilya Borisov commented on IGNITE-9811: -- [~pkonstantinov] fixed on sign in page, won't fix on sign up. > Web Console: Do not block "Save" button in case some inputs are invalid > --- > > Key: IGNITE-9811 > URL: https://issues.apache.org/jira/browse/IGNITE-9811 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > > Let's not block "Save" button in case some inputs invalid. > In modern UI trends it is better to set focus to invalid filed and show > tooltip with error when user clicked on "Save" button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692628#comment-16692628
]
Ilya Borisov commented on IGNITE-9339:
--
2. Fixed, but not the way I anticipated. I've added a "gigabytes" scale that
only has GB and TB. Default value is in GBs.
3. Done.
4. Done.
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
> 4. Fix validation error icon position:
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-9339:
Assignee: Ilya Borisov (was: Alexander Kalinin)
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
> 4. Fix validation error icon position:
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9339) Web console: form-field-size improvements
[
https://issues.apache.org/jira/browse/IGNITE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692628#comment-16692628
]
Ilya Borisov edited comment on IGNITE-9339 at 11/20/18 4:25 AM:
1. Let's do this in another issue or not at all.
2. Fixed, but not the way I anticipated. I've added a "gigabytes" scale that
only has GB and TB. Default value is in GBs.
3. Done.
4. Done.
was (Author: klaster_1):
2. Fixed, but not the way I anticipated. I've added a "gigabytes" scale that
only has GB and TB. Default value is in GBs.
3. Done.
4. Done.
> Web console: form-field-size improvements
> -
>
> Key: IGNITE-9339
> URL: https://issues.apache.org/jira/browse/IGNITE-9339
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Minor
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I think there some changes due for {{form-field-size}} component:
> 1. [~pkonstantinov] expressed his confusion multiple times about the fact
> that {{form-field-size}} converts visible value when user changes scale. He
> suggests to keep the view value the same and only scale the model value.
> 2. It wasn't the case at the moment {{form-field-size}} was added, but now
> some form fields use different default scale (i.e. it's bytes vs megabytes).
> [~Dmitriyff] introduced redundant "time" scale in IGNITE-9286, surely we can
> figure out a better component API for cases like this.
> 3. Add autofocus support.
> 4. Fix validation error icon position:
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10318) Web console: use newer panels in query notebook screen
[ https://issues.apache.org/jira/browse/IGNITE-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10318: - Assignee: Andrey Novikov (was: Ilya Borisov) > Web console: use newer panels in query notebook screen > -- > > Key: IGNITE-10318 > URL: https://issues.apache.org/jira/browse/IGNITE-10318 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Andrey Novikov >Priority: Minor > Attachments: How query notebook screen look now.png > > Original Estimate: 72h > Remaining Estimate: 72h > > "Queries notebook" screen is the last place where older style of collapsible > panels has remain in use. > What to do: > 1. Replace panels on "queries notebook" screen with panel-collapsible > component. > 2. Update query rename feature to use "Rename" button and new name prompt > instead on inline form. > 3. Move query remove button to context menu in panel actions. > 4. Move "Execute", "Execute on selected node", "Explain" and "Scan" button to > panel actions. All actions, except for "Execute" and "Scan", should be in > context menu. > 5. Remove legacy code used in older style collapsible panels. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9811) Web Console: Do not block "Save" button in case some inputs are invalid
[ https://issues.apache.org/jira/browse/IGNITE-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9811: Assignee: Alexey Kuznetsov (was: Alexander Kalinin) > Web Console: Do not block "Save" button in case some inputs are invalid > --- > > Key: IGNITE-9811 > URL: https://issues.apache.org/jira/browse/IGNITE-9811 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > Let's not block "Save" button in case some inputs invalid. > In modern UI trends it is better to set focus to invalid filed and show > tooltip with error when user clicked on "Save" button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9811) Web Console: Do not block "Save" button in case some inputs are invalid
[
https://issues.apache.org/jira/browse/IGNITE-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691265#comment-16691265
]
Ilya Borisov commented on IGNITE-9811:
--
I've updated the validation directives to work with tooltip-style validation
messages too. Call {{IgniteFormUtils.triggerValidation(form)}} to focus invalid
fields and show error messages. The form on user edit screen has been updated
to behave like requested.
> Web Console: Do not block "Save" button in case some inputs are invalid
> ---
>
> Key: IGNITE-9811
> URL: https://issues.apache.org/jira/browse/IGNITE-9811
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexander Kalinin
>Priority: Major
>
> Let's not block "Save" button in case some inputs invalid.
> In modern UI trends it is better to set focus to invalid filed and show
> tooltip with error when user clicked on "Save" button.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9811) Web Console: Do not block "Save" button in case some inputs are invalid
[
https://issues.apache.org/jira/browse/IGNITE-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691265#comment-16691265
]
Ilya Borisov edited comment on IGNITE-9811 at 11/19/18 5:14 AM:
I've updated the validation directives to work with tooltip-style validation
messages too. Call {{IgniteFormUtils.triggerValidation(form)}} to focus invalid
fields and show error messages. The form on user edit screen has been updated
to behave like requested.
[~kuaw26] please review.
was (Author: klaster_1):
I've updated the validation directives to work with tooltip-style validation
messages too. Call {{IgniteFormUtils.triggerValidation(form)}} to focus invalid
fields and show error messages. The form on user edit screen has been updated
to behave like requested.
> Web Console: Do not block "Save" button in case some inputs are invalid
> ---
>
> Key: IGNITE-9811
> URL: https://issues.apache.org/jira/browse/IGNITE-9811
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
>
> Let's not block "Save" button in case some inputs invalid.
> In modern UI trends it is better to set focus to invalid filed and show
> tooltip with error when user clicked on "Save" button.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
