Skip to content
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: introduction of not-exists operator (DEV-1845) #969

Merged
merged 7 commits into from Mar 27, 2023

Conversation

Vijeinath
Copy link
Collaborator

@Vijeinath Vijeinath commented Mar 24, 2023

resolves DEV-1845

Note: The case for linking properties (including unit tests) is commented out and will be activated later (DEV-1966)

@Vijeinath Vijeinath requested a review from mdelez as a code owner March 24, 2023 08:32
@Vijeinath Vijeinath self-assigned this Mar 24, 2023
@linear
Copy link

linear bot commented Mar 24, 2023

DEV-1845 Implementing "not exist" operator

Adding "not exist" to the advanced search to the app.

Copy link

@BalduinLandolt BalduinLandolt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I can see it looks good, but probably someone who knows the App could provide more valuable feedback.

Comment on lines +326 to +364
// it('should set the correct comparison operators for a linking property type (on top level)', () => {
// const resProps = MockOntology.mockReadOntology(
// 'http://0.0.0.0:3333/ontology/0001/anything/v2'
// ).getPropertyDefinitionsByType(ResourcePropertyDefinition);
//
// testHostComponent.propertyDef = resProps.filter(
// (propDef) =>
// propDef.id ===
// 'http://0.0.0.0:3333/ontology/0001/anything/v2#hasOtherThing'
// )[0];
//
// testHostFixture.detectChanges();
//
// expect(
// testHostComponent.specifyProperty.comparisonOperators.length
// ).toEqual(5);
// expect(testHostComponent.topLevel).toBeTrue();
// });

// it('should set the correct comparison operators for a linking property type (not on top level)', () => {
// const resProps = MockOntology.mockReadOntology(
// 'http://0.0.0.0:3333/ontology/0001/anything/v2'
// ).getPropertyDefinitionsByType(ResourcePropertyDefinition);
//
// testHostComponent.propertyDef = resProps.filter(
// (propDef) =>
// propDef.id ===
// 'http://0.0.0.0:3333/ontology/0001/anything/v2#hasOtherThing'
// )[0];
//
// testHostComponent.topLevel = false;
//
// testHostFixture.detectChanges();
//
// expect(
// testHostComponent.specifyProperty.comparisonOperators.length
// ).toEqual(4);
// expect(testHostComponent.topLevel).toBeFalse();
// });

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know about you frontend friends... but we tend to not want commented-out code in our codebase

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. It does not look good. As soon as the mystery with the linking property is solved, it will be uncommented

@Vijeinath Vijeinath merged commit 63c5136 into main Mar 27, 2023
10 checks passed
@Vijeinath Vijeinath deleted the wip/dev-1845-not-exist-operator-2 branch March 27, 2023 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants