UX issue: non-functional "Compile Component" button on absence of available components. #898

New Issue

Closed

opened 2022-04-17 03:28:31 +00:00 by kamilrafik · 2 comments

kamilrafik commented

2022-04-17 03:28:31 +00:00

(Migrated from github.com)

On the first screenshot you will see the button itself and on second the page that is rendered after click.
The button must be disabled on absence of available components.

On the first screenshot you will see the button itself and on second the page that is rendered after click. The button must be disabled on absence of available components. ![Screenshot from 2022-04-17 06-26-22](https://user-images.githubusercontent.com/4179340/163699026-49347979-b494-49c2-9beb-b4ce91e799bc.png) ![Screenshot from 2022-04-17 06-26-29](https://user-images.githubusercontent.com/4179340/163699031-da3ba941-3d61-4da2-86e1-40d1817483dd.png)

Llewellyn commented

2022-04-22 00:23:04 +00:00

Not sure I understand this issue... please explain more.

kamilrafik commented

2022-04-22 11:50:38 +00:00

(Migrated from github.com)

It is very minor non-significant issue in fact; I just documented it for the future.

Solution: just make "Compile Component" button disabled if there is no components in the system.

By default, there are some components in the system (at least Demo) that are listed in dropdown which you can choose and then compile by pressing "Compile Component" button. If you will delete all components, dropdown disappears, but "Compile Component" button still stays clickable; although, after click it redirects user to empty page. It is very minor non-significant issue in fact; I just documented it for the future. Solution: just make "Compile Component" button disabled if there is no components in the system.