-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix(react-components): list 360-core-dm-connected assets #4967
base: master
Are you sure you want to change the base?
Conversation
Does not include Search-capabilities
There were failures in the visual tests workflow. |
viewer/packages/data-providers/src/image-360-data-providers/cdm/queryFilters.ts
Outdated
Show resolved
Hide resolved
viewer/packages/360-images/src/collection/DefaultImage360Collection.ts
Outdated
Show resolved
Hide resolved
@@ -5,15 +5,17 @@ import { type ExternalId, type IdEither, type InternalId } from '@cognite/sdk'; | |||
import { type DmsUniqueIdentifier } from '../../data-providers'; | |||
import { type InstanceReference } from './types'; | |||
|
|||
export function isIdEither(instance: InstanceReference): instance is IdEither { | |||
export type AnnotationAssetRef = { externalId?: string; space?: 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.
Can't we use DmsUniqueIdentifier
directly?
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.
Ah, this is actually a mistake from my side 🙈 This is supposed to be the assetRef
field of the images.assetLink datatype of annotations. I've corrected it now to { id?: number; externalId?: string; }
@@ -153,3 +124,93 @@ function getObject3dRelation(visualizableTableName: string): QueryTableExpressio | |||
} | |||
}; | |||
} | |||
|
|||
// eslint-disable-next-line @typescript-eslint/explicit-function-return-type | |||
export function createCheck3dConnectedEquipmentQuery( |
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 see that we have too many properties been selected here in single query, was wondering if it could have any performance issue while fetching huge data for all resources
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.
Yes, it's quite a lot 😓 I'm sure it can be heavy for some queries, but in practice, I don't think there will be a huge amount of returned data. We're only looking for 3D-connections (including directly connected, indirect through reference and indirect through edge) in the different model types for a few specific input instances. I expect almost all such queries to return less than 100 results for each input instance in total
I swear, I could not for the life of me make the linter accept this.
Does not include Search-capabilities
Type of change
Jira ticket 📘
https://cognitedata.atlassian.net/browse/
Description 📝
Return coreDM-360-connected assets from the useSearch...-hook.
Not yet finished - next step is ensuring it also works with the search functionality.
Enables https://github.com/cognitedata/fusion/pull/11099
How has this been tested? 🔍
Test instructions ℹ️
Checklist ☑️