maqetta/maqetta — comment on commit 513030772447082e4a8bfff5c8931a080d53bd9b
File: davinci.html/WebContent/metadata/html/a_oam.json line 32
By aerwin:

The `unconstrained` attribute is necessary because in addition to (_self, _top, etc.) you can specify the id of any iframe [http://www.w3schools.com/html5/att_a_target.asp]).

In WidgetProperties.js, it was looking for `unconstrainted` (notice the misspelling) on the property itself. So, I had to change the existing code to spell it correctly so the condition would pass.

BUT, as I look at the link you sent, you are correct that the schema calls for `unconstrained` to be on `options`...

BUT, interestingly, in studying the schema further, it also says that `option` is only supposed to contain one item. But, no where in any of our OAM metadata files do I see anyone using `options` for multiple items. So, I think most of our OAM metadata files are violating the schema.

Do we want a separate issue to track making all of the OAM metadata files across Maqetta to conform to the schema (e.g., use `options` instead of `option`) and properly handle `unconstrained` as part of `options`?

For the last point, I'll add in the defaultValue.