It would be helpful in all React plugins to forward HTML properties to plugin container <div> tag.

Example usage:

<ProgressBar className="x" />

I would expect it will generate code:

<div class="x">
   <div class="uppy uppy-ProgressBar" style="position: initial;">
       <div class="uppy-ProgressBar-inner" style="width: 100%;"></div>
       <div class="uppy-ProgressBar-

Links to all modules are broken because of renaming

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question
• Discussion

I think that "Cancel" or "Close" btn need to be added to Create New content.

Once user change his mind to open it, there is no "Right" way to go back.

When you open page UI Elements -> Cards i see TABS are not showing content until you click on other and back on first, same for pills.

Possible fix : ( worked for me )

<script type="text/javascript"> $(document).ready(function(){ $('.nav-item').tab('show'); $('.nav-tabs li a:first').trigger('click'); }); </script>

Concept

We need a function in the config manager to easily extract values from a string list.
Ex: "1,2,3,4" or "1, 2, 3, 4"

In the module conf:
MyModule.List = "1, 2, 3, 4"

In the module cpp:

sConfigMgr->GetUint32ListDefault("MyModule.List", "")

Actually, everytime we want to make a list, we have to recreate a similar function in our modules. This is very bad
Maybe

I was wondering the benefit of using Modular File Management vs Single Config File Management? Why do you consider it easier to use multiple files and then compile? Trying to figure out what the best case is for my use case. Thanks. #