FLUID-5170: If primary schema has fewer prefs than auxiliary schema has, panels are still created without errors, they just don't work

Metadata

Source
FLUID-5170
Type
Bug
Priority
Blocker
Status
Closed
Resolution
Fixed
Assignee
N/A
Reporter
Anastasia Cheetham
Created
2013-10-04T16:11:55.187-0400
Updated
2013-10-28T10:32:33.884-0400
Versions
N/A
Fixed Versions
  1. 1.5
Component
  1. Prefs Framework

Description

If the aux schema includes panels and enactors for preferences that are not mentioned in the primary schema, then the panels will be rendered without any errors whatsoever, but they will be non-functional. It may be very hard for an integrator to diagnose the problem.

I would think we need to let the integrator know somehow that they're trying to render panels for prefs that aren't supported, either by not rendering the panels, or at least by throwing some kind of error or at least a warning in the console.

To reproduce:

Use the 'starter schema' demos
Edit the "StarterSchemas.js" file to comment out most of the primary preference schemas.
Watch the console, and run the demo.

You'll see that the panels are all there, but the ones for your commented-out prefs don't do anything, and you'll see that no errors appear in the console.

Comments