-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
required attribute not enforced #16
Comments
The same remark , i agree. |
Yes, required is not currently implemented. For the most part, attributes that effect how many of an element/attribute are allowed are not implemented at present. Those features have mostly just been added when other people contribute them. Implementing use="required" would be relatively simple compared to some of the other restrictions, it seems like it would just require updating: SchemaProcessor.prototype.build_attribute |
I changed XMLElement.prototype.populateChildren as you said but it didn't work . for(var i = 0; i < self.objectType.attributes.length; i++){ |
I mostly implemented this. The remaining problem is that I haven’t given the Add Attribute menu button to the call to XMLElement.prototype.populateChildren (instead I temporarily modified GUIEditor.prototype.addAttributeEvent to not require it, as a hack), because I don't see how to easily fetch it. This manifests when I delete the auto-added attribute; the Add Attribute menu doesn’t immediately update appropriately (to allow you to re-add the attribute), though it does if you switch editors and then switch back. @bbpennel, is there an easy way to get a pointer to the button labeled X in the currently-visible Add Attribute menu when the currently-selected element has X as a possible attribute? |
Hi, |
For reference, this topic is also discussed in #55. |
required attribute is not automatically added to the element, and also can be deleted after the attribute is added manually.
The text was updated successfully, but these errors were encountered: