-
Notifications
You must be signed in to change notification settings - Fork 4
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
DSP-974 / DSP-1043 Determine from ontology if a property is read-only #233
Conversation
addButtons = propertyViewComponentDe.queryAll(By.css('button.create')); | ||
expect(addButtons.length).toEqual(20); | ||
expect(addButtons.length).toEqual(18); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a better way to know the number of expected buttons than to write a hardcoded number? Maybe we can use the propArray to check how many properties are not read-only and use that? This way if the test data changes, we don't have to keep manually updating the number. Idk how it will work with cardinalities though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some explicit tests in 186d024
resolves DSP-974 and DSP-1043
ValueService.isReadOnly
has an additional third argument now:propertyDef: ResourcePropertyDefinition
.I added the flag "breaking" because this method could be used directly by the app.