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
feat(ontology): refactor list of properties in resource class (DSP-1360) #389
feat(ontology): refactor list of properties in resource class (DSP-1360) #389
Conversation
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.
- There are some index, e.g. 0) 1), that are doubled or tripled, or even missing, e.g. 0) -> 2)
- Is it normal behaviour to be able to click on the referred list but not on the linked resource?
- Maybe only on my local app: For the BEOL ontologies, I have an error message in the console.log: "Cannot read property 'label' of undefined" -
property-info.component.ts:95
The Gui order is defined in the ontology; it's part of the res class cardinality. In case of missing or doubled numbers it's a mistake in the ontology. The test data are not well done.
Yes. At the moment we do not have a native route for the linked resource class. I was thinking to highlight the linked class somehow. But this will take more time.
I will check this... |
I have the same console error. The BEOL ontology also has a lot of empty resource classes at the bottom for some reason. Maybe that's the issue @kilchenmann? EDIT: Actually, the Biblio ontology has 36 of these console errors and doesn't contain any empty resource classes, |
Yes there's something weird with the ontology test-data in some projects. I will spend some time to do some investigations. Maybe someone of you can help me with that? |
I already found something: the empty resource classes doesn't have a label. They are all of type "Standoff"-something. Will try to fix it; standoff doesn't have to be displayed |
it('should create', () => { | ||
expect(testHostComponent).toBeTruthy(); | ||
}); | ||
}); |
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 would add a test here to ensure the component is receiving the correct data for propDef
, propCard
, and projectcode
via the @Input
s
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.
@kilchenmann please add these assertions and then I will approve :)
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.
Will add it this evening.
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.
done in 8cf574e
|
||
@Input() propCard: IHasProperty; | ||
|
||
@Input() projectcode: string; |
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.
projectcode -> projectCode
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.
it's the same as in other components. To be consistent, I have to change it everywhere. But I can do it...
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've noticed it elsewhere as well. Maybe leave it for now and we can open a small PR to rename them everywhere all at once.
I found the problem. The linked resource is defined in another ontology. The ontology editor is not yet prepared for this case. It will make the things more complex 🙈 ... but fine, I'll fix it. |
It seems to be fixed now. I had to integrate new cache for |
great, so as soon as you merge this, please make a release and deploy it to test and staging. thanks. |
resolves DSP-1360 (bug fix by returning resource class and properties in all languages)
incl. refactoring of cache and ontology editor in general.
The ontology editor lists the resource classes with new list of corresponding properties; the design contains: