Continuing from @himdel's comment: #83 (comment)

So.. I've updated the script to output $? after commit and push, just to verify the push isn't succeeding somewhere.. but I'm pretty much stumped. As in, can't continue without seeing the actual error message from git push.. @Fryguy I think you'll have to look into this, sorry :).

The script works, both on travis and locally, if I run the same with --dry-run and my credentials, the push pretends to succeed, so .. possibly a wrong GITHUB_AUTH value, or wrong syntax, or a leading/trailing space in the value or something like that...

See https://travis-ci.org/ManageIQ/ui-components#L966-L1114 as an example

cc @skateman

Add support for semantic release so we can release package updates to NPM seamlessly.

here's the outcome of compiling - on Fedora 24:

• I get this warning on incompatibility:
  "warning [email protected]: The platform "linux" is incompatible with this module."
  given that miq is running on linux - sounds like this warning should be resolved

ActionController::RoutingError (No route matches [GET] "/assets/@manageiq/ui-components/dist/js/ui-components.js.map")
ActionController::RoutingError (No route matches [GET] "/assets/@manageiq/ui-components/dist/css/ui-components.css.map")

@miq-bot assign @himdel

@skateman suggested we should have a script to generate a new empty component with all the boilerplate needed .. sounds like a good idea :).

I'm guessing http://yeoman.io/?

(Mostly creating this issue so that I don't forget, but if anyone wants to take this.. :) )

There's been a few discussion around the topic of not having dist/ in git, to prevent useless merge conflicts, etc.

Seems like there's 2 options - separate repo for the built package, or gitignore dist/ and git add --force the files. Either relies on travis updating dist/ when doing a successful master build.

Creating the issue so we can have 1 place for the discussion on how to do that...

Cc @mtho11 , @martinpovolny , @karelhala , @skateman

CVE-2022-25869 - Medium Severity Vulnerability

Vulnerable Library - angular-1.8.3.tgz

HTML enhanced for web apps

Library home page: https://registry.npmjs.org/angular/-/angular-1.8.3.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/angular-bootstrap-switch/node_modules/angular/package.json

Dependency Hierarchy:

• angular-bootstrap-switch-0.5.2.tgz (Root Library)
  • ❌ angular-1.8.3.tgz (Vulnerable Library)

Found in HEAD commit: a5db0714038685437d759b29eb80b4b9e415b2c2

Found in base branch: master

Vulnerability Details

All versions of package angular are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of <textarea> elements.

Publish Date: 2022-07-15

URL: CVE-2022-25869

CVSS 3 Score Details (4.2)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Step up your Open Source Security Game with Mend here

Hi guys.
The "multiselect" options for DropDown list does not work in SUI. I cannot select multiple values for this type of element form SUI but can do it from classic ui:
Screen frim Classic UI:

Screen from SUI:

Service have dynamic dialog with dropdown element with "multiselect" option:

As mentioned in: #318 , the styling of radio buttons in the dynamic dialog is non-standard (radio buttons wrapped in a label with "btn btn-primary" classes applied)

vs

@chalettu @eclarizio Any idea what the rationale might have been for styling them that way? Do you see any issues with changing it from the SUI perspective?

cc\ @Rohoover @terezanovotna @Loicavenel

We are lacking quadicon component, right now it's generated on server and rendered as HTML object inside grid or tile.

Improvements

Click action is now really complex and inside of it it's calculated what screen and what action should be triggered.
We could use more complex actions and show more information based on each quadicon.

Per @Loicavenel we expect when a checkbox is "required", that means that it needs to validate as being checked. Any other state should produce an error.

It's really enough in development to be able to display the ff icons in the fonticon-picker.

I'm getting an error describing missing selectpicker function while testing a dialog editor in ui-components demo page:

Error: element.selectpicker is not a function
link@http://localhost:4000/js/vendor.js:13447:7
bind/<@http://localhost:4000/js/vendor.js:40662:15
cloneAndAnnotateFn/<@http://localhost:4000/js/vendor.js:49549:41
invokeLinkFn@http://localhost:4000/js/vendor.js:49555:9
nodeLinkFn@http://localhost:4000/js/vendor.js:48954:11
compositeLinkFn@http://localhost:4000/js/vendor.js:48213:13
compositeLinkFn@http://localhost:4000/js/vendor.js:48216:13
publicLinkFn@http://localhost:4000/js/vendor.js:48093:30
lazyCompilation@http://localhost:4000/js/vendor.js:48450:16
boundTranscludeFn@http://localhost:4000/js/vendor.js:48230:16
controllersBoundTransclude@http://localhost:4000/js/vendor.js:49004:20
ngIfWatchAction@http://localhost:4000/js/vendor.js:66510:15
$digest@http://localhost:4000/js/vendor.js:57239:23
$apply@http://localhost:4000/js/vendor.js:57505:13
timeout/timeoutId<@http://localhost:4000/js/vendor.js:59353:25
completeOutstandingRequest@http://localhost:4000/js/vendor.js:45448:7
Browser/self.defer/timeoutId<@http://localhost:4000/js/vendor.js:45727:7
 <select class="form-control ng-pristine ng-untouched ng-valid ng-isolate-scope" pf-select="" ng-model="vm.fieldData.default_value">

/cc @skateman @karelhala

While updating service dialogs by values from automate, the validation does not get updated automatically. After hover action, the Submit button gets enabled:

Rename the new dialog component to dialog-user.

Please move the field error message below input fields on the new dialog component recently contributed in PR#82.

Below is a screenshot of the current implementation:

Based on the PF guidelines, "Text input fields with validation errors are indicated with a red border around the input box and a Field Error Message below the field describing the error."

Node 6.x is LTS is good, but 7.x stable doesn't run (at least on OS/X). Since it is the stable version and we are in Dev, it should probably also run in 7.x.

Child extract-text-webpack-plugin:
+ 1 hidden modules

ERROR in Missing binding ui-components/node_modules/node-sass/vendor/darwin-x64-51/binding.node
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 7.x

Found bindings for the following environments:
  - OS X 64-bit with Node.js 6.x

This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to build the binding for your current environment.

When testing with the regex string \A[\w+-.]+@[a-z\d-]+(.[a-z]+)*.[a-z]+\z
the API returns \\A[\\w+\\-.]+@[a-z\\d\\-]+(\\.[a-z]+)*\\.[a-z]+\\z I think the escaped \\ is causing our regex validation to not work. Investigate issue and fix.

CVE-2023-26116 - Medium Severity Vulnerability

Vulnerable Library - angular-1.8.3.tgz

HTML enhanced for web apps

Library home page: https://registry.npmjs.org/angular/-/angular-1.8.3.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/angular-bootstrap-switch/node_modules/angular/package.json

Dependency Hierarchy:

• angular-bootstrap-switch-0.5.2.tgz (Root Library)
  • ❌ angular-1.8.3.tgz (Vulnerable Library)

Found in HEAD commit: a5db0714038685437d759b29eb80b4b9e415b2c2

Found in base branch: master

Vulnerability Details

Versions of the package angular from 1.2.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the angular.copy() utility function due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking.

Publish Date: 2023-03-30

URL: CVE-2023-26116

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Step up your Open Source Security Game with Mend here

Add capability to disable table cols:

cols: [
  {
    header_text: 'col1',
    col_idx: 1,
    hidden: true // cols with such option won't be shown
  },
  {
    header_text: 'col1',
    col_idx: 1,
    hidden: true
  }
]

First column uses for select box, but if we don't use select box, first column still is shown
We have no way to disable first column

Add check if there are select boxes

https://github.com/ManageIQ/ui-components/blob/master/src/gtl/components/data-table/data-table.html#L17

ERROR in ./src/tree-view/treeViewComponent.ts
[73, 1]: Exceeds maximum line length of 120
[74, 1]: Exceeds maximum line length of 120

The problem is that there are one-liner functions with the fat arrow syntax and they behave differently when rewritten to multiline ones. Any idea @karelhala @himdel?

When toolbars are used we need to specify color for it's icon in JSON.

Requested by @skateman for future color picker.

Current state:

Expected state:

Given field with values of "one", "two", "three", it makes absolutely no sense whatsoever to be able to set the default value to "four". And yet you can!

This is placeholder issue for someone who is not involved in merge process, we have abandoned typings package in #41 so if you had installed this package before this transition. Remove folder typings and node_modules and re-run npm install to check types from npm.

When prepublish fails, publish gets run anyway.

As of npm 5, prepublish is deprecated in favor of prepare.

We do have a bunch of inline style declarations that we probably want in CSS instead.

Just so as not to forget, raised in #37 .

In this issue I'll keep a list of known issues in the dialog editor, I'll keep it as WIP, until I describe the issues properly with all the details.

bugs, missing features:

• missing spinner
• update multiselect dropdown to save the default values as string ("value" - normal, "value1,value2" - multiselect
• tag control without set automate methods gives errors (#173)
• flash messages (partially fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1514117) - maybe display the error message on the save button with the same popup, we use for showing help info on dialog editor fields (maybe this could help: https://plnkr.co/edit/bdFVmZagG1APgKj0qGHp?p=info)
• validations for fields (https://github.com/ManageIQ/manageiq-ui-classic/blob/33f26e217cce49a53de87733ce1de6b53a2e4a4e/app/controllers/miq_ae_customization_controller/dialogs.rb#L705, https://gitter.im/ManageIQ/manageiq/automate?at=5a258b6a71ad3f873665cb3f)
• if the bootstrap switch is undefined, mark it as false
• saving of intermediate state into localStorage
• [ ] validation - drag Tag Control into a empty dialog with a title - the validation says "Dialog needs to have a label" instead of "Category needs to be set for TagControl field". Setting a Category and un-setting it produces the correct error message.

refactoring:

• DRY code for dialog editor (there's a lot of copypasted code right now: #170 (comment))
• correct naming in code (elements -> fields, box -> group, etc.)
• #98

http://www.patternfly.org/pattern-library/content-views/canvas-view/

It feels confusing to me that requests for VM provision are listed in Services menu (Services => Requests), since we have Requests in Infrastructure too (Compute => Infrastructure => Requests).

It would make more sense to me if Infra & Cloud request would be listed in Compute menu, for example in new 2nd level item (Compute => Requests) instead of in Services.

@martinpovolny @dclarizio

This issue was moved to this repository from ManageIQ/manageiq#11354, originally opened by @romanblanco

Please update the styles of the radio buttons in the new dialog component recently contributed in #82.

Current visualization:

PatternFly radio buttons can be seen here: http://www.patternfly.org/pattern-library/forms-and-controls/data-input/#/radio-buttons

I think you should be able to set values for text boxes in new editor. It's a dialog field, and they have values. Why can't you set a value in the editor?

After changing a dynamic dropdown to no longer be dynamic, the button for adding entries is present but does nothing at all when clicked. Not being able to add entries means the dialog fails validation.

This issue was moved to this repository from ManageIQ/manageiq-ui-classic#3981, originally opened by @d-m-u

https://files.gitter.im/PanSpagetka/3npj/Screenshot-from-2016-09-20-10-33-05.png

Happens during

ManageIQ.toolbars.hideItem('#center_tb', 'perf_refresh');
ManageIQ.toolbars.hideItem('#center_tb', 'perf_reload');

in VM's Utilization screen.

@karelhala the usual question :) (I have not yet tried to figure out if this is because the button didn't exist or something like that, but we should probably not crash anyway..)

Now that the decision has been made to remove the old tile view (https://bugzilla.redhat.com/show_bug.cgi?id=1734182), it would be a great time to deal with another complication: When GTL was moved to Ui-components, a decision was made to wrap both the Tiles and Quadicons in a pf-card and display them on a gray background. This was not only inconsistent with list view but created enormous headaches on the classic side in rendering the gray background properly.

I would like to remove the card from the quads (see below), remove the gray background from that view and get rid of all the spaghetti logic on the classic side that will cause nothing but problems as we move forward.

Current

New

Current Listview

We might want to think about using Typedoc for our typescript documentation.

Here is sample of a project using it: http://molecuel.github.io/mlcl_core/classes/mlclcore.html#subjects

wdyt?

CC @karelhala @himdel @martinpovolny

The Karma tests are failing:

PhantomJS 2.1.1 (Mac OS X 0.0.0) Sort items test controller should init options FAILED
TypeError: undefined is not a constructor (evaluating 'compileProvider.preAssignBindingsEnabled()') (line 2260)
node_modules/angular-mocks/angular-mocks.js:2260:80
$componentController@node_modules/angular-mocks/angular-mocks.js:2330:25
src/common/components/sortItemsComponent.spec.ts:9:4093
invoke@dist/js/vendor.js:4828:25
WorkFn@node_modules/angular-mocks/angular-mocks.js:3151:26
inject@node_modules/angular-mocks/angular-mocks.js:3121:46
src/common/components/sortItemsComponent.spec.ts:9:3950
loaded@http://localhost:9876/context.js:151:17
inject@node_modules/angular-mocks/angular-mocks.js:3118:28
src/common/components/sortItemsComponent.spec.ts:9:3950
loaded@http://localhost:9876/context.js:151:17
TypeError: undefined is not an object (evaluating 'sortItemsCtrl.options') in src/common/components/sortItemsComponent.spec.ts (line 9)
src/common/components/sortItemsComponent.spec.ts:9:6340
loaded@http://localhost:9876/context.js:151:17

Steps to Reproduce

npm cache clean
bower cache clean
rm -rf node_modules libs
npm install
npm test

Dialog Editor common component should reflect the latest UX Designs

Design work for the dialog editor can be found here: https://manageiq.github.io/manageiq-design/UX/ui-service/designer/Dialogs/design

When the dialog editor was part of the Service Designer, I think that Dave Taylor made many of the updates, unsure if they have been folded into the common component

@Loicavenel FYI

miq-pagination consists of miq-sort-items, miq-paging and select all checkbox

when paginationCtrl.settings.hideSelect is set, miq-pagination is hidden instead of only select all checkbox part

https://github.com/ManageIQ/ui-components/blob/master/src/gtl/components/pagination/pagination.html#L1

if tableCtrl.settings.sortBy isn't true, also miq-pagination is hidden instead of miq-sort-items part

it checks here
https://github.com/ManageIQ/ui-components/blob/master/src/gtl/components/data-table/data-table.html#L4

we need to check tableCtrl.settings.sortBy only here:
https://github.com/ManageIQ/ui-components/blob/master/src/gtl/components/pagination/pagination.html#L18

also pagination isn't hidden, when settings.isLoading == true
https://github.com/ManageIQ/ui-components/blob/master/src/gtl/components/data-table/data-table.html#L4

Seems this was missed in the larger conversion.

I'm getting the following error in javascript console on current ManageIQ master:

angular.self-4d4ad11d5ffcf4b45937b602ad6794ec0402cf414a488a6e28edf2a00bb8370c.js?body=1:14801 TypeError: Cannot read property 'includes' of undefined
    at toolbarComponent.ts:154
    at Array.filter (<anonymous>)
    at toolbarComponent.ts:154
    at baseFindIndex (lodash.self-ab7f9fcc194a42c87faff5feeff131a1afe3a245de9ccc9563c7b136fb125f2e.js?body=1:327)
    at Function.findLastIndex (lodash.self-ab7f9fcc194a42c87faff5feeff131a1afe3a245de9ccc9563c7b136fb125f2e.js?body=1:3262)
    at e.collapseButtons (toolbarComponent.ts:154)
    at e.$onChanges (ui-components.js:4653)
    at angular.self-4d4ad11d5ffcf4b45937b602ad6794ec0402cf414a488a6e28edf2a00bb8370c.js?body=1:9960
    at forEach (angular.self-4d4ad11d5ffcf4b45937b602ad6794ec0402cf414a488a6e28edf2a00bb8370c.js?body=1:417)
    at nodeLinkFn (angular.self-4d4ad11d5ffcf4b45937b602ad6794ec0402cf414a488a6e28edf2a00bb8370c.js?body=1:9956)

from gitter ☝️ August 29, 2019 11:47 AM

(same issue as ManageIQ/manageiq-ui-classic#5589,
likely the fix is to update node-sass to 4.12, same as ManageIQ/manageiq-ui-classic#6008)

cc @romanblanco

After draging Tag Control element into the Dialog Box, I'm getting error in console:

columnNumber : 73
fileName : "http://localhost:3000/assets/angular-patternfly-sass/dist/angular-patternfly.self-e808720f9b22bfc2fb44a48578a1b1a7d8d09ac62b8c01ad34e0589850b2ae53.js?body=1"
lineNumber : 6664
message : "ngModel is null"
stack : "link@http://localhost:3000/assets/angular-patternfly-sass/dist/angular-patternfly.self-e808720f9b22bfc2fb44a48578a1b1a7d8d09ac62b8c01ad34e0589850b2ae53.js?body=1:6664:73\nbind/<@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:1386:15\ncloneAndAnnotateFn/<@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:10540:41\ninvokeLinkFn@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:10546:9\nnodeLinkFn@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9935:11\ncompositeLinkFn@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9175:13\npublicLinkFn@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9040:30\nlazyCompilation@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9431:16\nboundTranscludeFn@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9218:16\ncontrollersBoundTransclude@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:9985:20\nngSwitchWatchAction/<@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:32166:13\nforEach@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:411:11\nngSwitchWatchAction@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:32165:11\n$digest@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:18262:23\n$apply@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:18532:13\ntimeout/timeoutId<@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:20449:25\ncompleteOutstandingRequest@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:6363:7\nBrowser/self.defer/timeoutId<@http://localhost:3000/assets/angular/angular.self-7e0b2baf4553bcd25cbb45cbe35556b3c2fbcb170db636503b5bee55a75e7b9b.js?body=1:6643:7\n"

I'm seeing a case where the miq-toolbar-group is generated (vm.hasContent(item) returns true) but not shown because it's empty..

To the left of the Configuration button..

This is the toolbarItem value:

[{"id":"history_choice","type":"buttonSelect","img":"history_choice.png","imgdis":"history_choice.png","icon":"fa fa-arrow-left fa-lg","name":"history_choice","hidden":false,"pressed":null,"onwhen":null,"data":null,"enabled":false,"title":"History","items":[],"explorer":true,"$$hashKey":"object:171"}]

Pretty sure the group should be hidden if empty, so hasContent should return false in this case.

@karelhala can you look into it please or should I?

Affects both Japanese and French translations but may also affect others.

Right now, a custom toolbar is just ng-bind-html...

Which is unfortunate because it doesn't $compile anything so the html can't really be angulary.
.. And you can't miq_boostrap because it's a child of the toolbar element, which has already been bootstrapped.

So.. to be able to use angulary custom toolbars, we may need to add support for components, or possibly a generic "$compile this" flag..

Per @Loicavenel, if a field has a regular expression check defined on it, it should run field validations whether or not the field itself is "required". The implementation needs to account for allowing blank to be considered as valid input since the field is optional. It needs to disable submission if someone edits the field and the field doesn't match validation regex.

bitHound discovered:

• 4 packages with at least one security vulnerability.
• 9 outdated packages.

For details go to bitHound.

Has anyone had such bug? I have this bug when try to use miq-data-table in manageiq-ui-service

Right now we have GTL view which includes pagination and GTL item directly, it would be nice to have component just for each GTL object (small/big tile, table). This way we could use this (any GTL item) component wherever we want without pagination.

EDIT: Also this might be interesting to UX team as well. Since we will be working with tables and refactoring them, how about we unify the styles and discuss what exactly is needed for each type of view.
Basically I think we have 2 questions.

1. Which types do we want?
   Grid is fine I guess, however what about tiles and table? I remember that we wanted to change this to something else, perhaps list-view?
2. Are we happy with how Grid looks like? Are there any things that can be improved?

This issue might be broken apart a couple of PRs, it's just to start discussion and to move forward something more usable and UX friendly.

I'm getting FATAL errors in console for some time now, informing me that ui-components.js.map is missing:

[----] I, [2016-09-20T13:17:11.489026 #2775:2b1b6568b450]  INFO -- : Started GET "/assets/manageiq-ui-components/dist/js/ui-components.js.map" for ::1 at 2016-09-20 13:17:11 +0200
[----] F, [2016-09-20T13:17:11.540451 #2775:2b1b6568b450] FATAL -- :   
[----] F, [2016-09-20T13:17:11.540801 #2775:2b1b6568b450] FATAL -- : ActionController::RoutingError (No route matches [GET] "/assets/manageiq-ui-components/dist/js/ui-components.js.map"):
[----] F, [2016-09-20T13:17:11.540858 #2775:2b1b6568b450] FATAL -- :   
[----] F, [2016-09-20T13:17:11.540898 #2775:2b1b6568b450] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
[----] F, [2016-09-20T13:17:11.540934 #2775:2b1b6568b450] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
[----] F, [2016-09-20T13:17:11.540980 #2775:2b1b6568b450] FATAL -- : railties (5.0.0.1) lib/rails/rack/logger.rb:36:in `call_app'
[----] F, [2016-09-20T13:17:11.541017 #2775:2b1b6568b450] FATAL -- : railties (5.0.0.1) lib/rails/rack/logger.rb:26:in `call'
[----] F, [2016-09-20T13:17:11.541053 #2775:2b1b6568b450] FATAL -- : request_store (1.3.1) lib/request_store/middleware.rb:9:in `call'
[----] F, [2016-09-20T13:17:11.541085 #2775:2b1b6568b450] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/request_id.rb:24:in `call'
[----] F, [2016-09-20T13:17:11.541116 #2775:2b1b6568b450] FATAL -- : rack (2.0.1) lib/rack/method_override.rb:22:in `call'
[----] F, [2016-09-20T13:17:11.541148 #2775:2b1b6568b450] FATAL -- : rack (2.0.1) lib/rack/runtime.rb:22:in `call'
[----] F, [2016-09-20T13:17:11.541178 #2775:2b1b6568b450] FATAL -- : activesupport (5.0.0.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
[----] F, [2016-09-20T13:17:11.541210 #2775:2b1b6568b450] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/executor.rb:12:in `call'
[----] F, [2016-09-20T13:17:11.541274 #2775:2b1b6568b450] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/static.rb:136:in `call'
[----] F, [2016-09-20T13:17:11.541314 #2775:2b1b6568b450] FATAL -- : rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
[----] F, [2016-09-20T13:17:11.541346 #2775:2b1b6568b450] FATAL -- : rack-mini-profiler (0.10.1) lib/mini_profiler/profiler.rb:171:in `call'
[----] F, [2016-09-20T13:17:11.541380 #2775:2b1b6568b450] FATAL -- : railties (5.0.0.1) lib/rails/engine.rb:522:in `call'
[----] F, [2016-09-20T13:17:11.541411 #2775:2b1b6568b450] FATAL -- : puma (3.3.0) lib/puma/configuration.rb:224:in `call'
[----] F, [2016-09-20T13:17:11.541442 #2775:2b1b6568b450] FATAL -- : puma (3.3.0) lib/puma/server.rb:561:in `handle_request'
[----] F, [2016-09-20T13:17:11.541473 #2775:2b1b6568b450] FATAL -- : puma (3.3.0) lib/puma/server.rb:406:in `process_client'
[----] F, [2016-09-20T13:17:11.541503 #2775:2b1b6568b450] FATAL -- : puma (3.3.0) lib/puma/server.rb:271:in `block in run'
[----] F, [2016-09-20T13:17:11.541533 #2775:2b1b6568b450] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread'

is there something, that can be done to fix this? 😊 @karelhala

When a Dialog Element is set Required = True, we should show an information in the Dialog. I thought we were putting a “*” but discovered this is not the case. User will find out when clicking submit….. I think this is a pretty simple and will help a lot.