Just last week it looks like IBM added a new custom control Drill Down (expand or collapse) to the IBM Accelerator Catalog however it doesn't work as uploaded.

Problems:

• Jquery was having a conflict with scope
• Extension name and path folder mismatch in the spec.json and designModule.js
  • Extension Name: "Drill_down"
  • Path Example: "v1/ext/drill_down/symbols.svg"
  • Uppercase mismatch 
• An extra _MACOSX folder that is unneeded
• Bug: where the initial state for a List control wouldn't respect the startState = expanded.
• No Configuration included
• No example report
• Poorly written instructions on how to import and use the extension.
  • Lacks enough detail and found some spelling errors and possible mistakes.
• Code Comments were a bit unprofessional

I went through the code and fixed the problem issues and changed the code a little bit.

• A default configuration loads automatically as a native custom control
• The control type is now inferred by the specname of the specified control
• I included an example report (12.0.4+) that shows how to use this custom control and attached it below.
  
• Configuration: {
      "Control Name": "List1",
      "Start Expanded": true
  }
• Added Error Handling

I appreciate the new native custom control features being added to the accelerator catalog however I think there needs to be more quality control while testing and approving official IBM accelerators custom controls. I also had an issue using the other newest custom control because it had another spec.json issue and would not load in my environment without extra tweaking. If these features don't work out of the box there is no reason to trust IBM code quality and it will hurt new developers trying to learn and write new code.  

Just last week it looks like IBM added a new custom control Drill Down (expand or collapse) to the IBM Accelerator Catalog however it doesn't work as uploaded.

Problems:

• Jquery was having a conflict with scope
• Extension name and path folder mismatch in the spec.json and designModule.js
  • Extension Name: "Drill_down"
  • Path Example: "v1/ext/drill_down/symbols.svg"
  • Uppercase mismatch 
• An extra _MACOSX folder that is unneeded
• Bug: where the initial state for a List control wouldn't respect the startState = expanded.
• No Configuration included
• No example report
• Poorly written instructions on how to import and use the extension.
  • Lacks enough detail and found some spelling errors and possible mistakes.
• Code Comments were a bit unprofessional

I went through the code and fixed the problem issues and changed the code a little bit.

• A default configuration loads automatically as a native custom control
• The control type is now inferred by the specname of the specified control
• I included an example report (12.0.4+) that shows how to use this custom control and attached it below.
  
• Configuration: {
      "Control Name": "List1",
      "Start Expanded": true
  }
• Added Error Handling

I appreciate the new native custom control features being added to the accelerator catalog however I think there needs to be more quality control while testing and approving official IBM accelerators custom controls. I also had an issue using the other newest custom control because it had another spec.json issue and would not load in my environment without extra tweaking. If these features don't work out of the box there is no reason to trust IBM code quality and it will hurt new developers trying to learn and write new code.  

------------------------------
Michael Webb
------------------------------

Just last week it looks like IBM added a new custom control Drill Down (expand or collapse) to the IBM Accelerator Catalog however it doesn't work as uploaded.

Problems:

• Jquery was having a conflict with scope
• Extension name and path folder mismatch in the spec.json and designModule.js
  • Extension Name: "Drill_down"
  • Path Example: "v1/ext/drill_down/symbols.svg"
  • Uppercase mismatch 
• An extra _MACOSX folder that is unneeded
• Bug: where the initial state for a List control wouldn't respect the startState = expanded.
• No Configuration included
• No example report
• Poorly written instructions on how to import and use the extension.
  • Lacks enough detail and found some spelling errors and possible mistakes.
• Code Comments were a bit unprofessional

I went through the code and fixed the problem issues and changed the code a little bit.

• A default configuration loads automatically as a native custom control
• The control type is now inferred by the specname of the specified control
• I included an example report (12.0.4+) that shows how to use this custom control and attached it below.
  
• Configuration: {
      "Control Name": "List1",
      "Start Expanded": true
  }
• Added Error Handling

I appreciate the new native custom control features being added to the accelerator catalog however I think there needs to be more quality control while testing and approving official IBM accelerators custom controls. I also had an issue using the other newest custom control because it had another spec.json issue and would not load in my environment without extra tweaking. If these features don't work out of the box there is no reason to trust IBM code quality and it will hurt new developers trying to learn and write new code.  

------------------------------
Michael Webb
------------------------------