Skip to content

Conversation

@devnaumov
Copy link
Member

closes 5145

Comment on lines +309 to +315
if (node.objectFeatures.includes(EObjectFeature.dataSource)) {
return node.id;
}

const parts = node.id.split('/');
parts.splice(parts.length - 1, 1, name);
const path = parts.join('/');
Copy link
Member

Choose a reason for hiding this comment

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

if it possible we should avoid such conditions in the generic places

Copy link
Member Author

Choose a reason for hiding this comment

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

We can ignore it on the subscription level, but then we need to do it in every place, the connection node is just a node which id behaves differently when renaming, i think it would be strange to submit event with invalid nodeId,

I think the best optoin is to return new id from backend

Copy link
Member

Choose a reason for hiding this comment

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

agree, best option is to get new id from the backend

Comment on lines -116 to +117
return node.features?.includes(ENodeFeature.canRename) ?? false;
return (node.features?.includes(ENodeFeature.canRename) || node.objectFeatures.includes(EObjectFeature.dataSource)) ?? false;
Copy link
Member

Choose a reason for hiding this comment

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

seems strange, why backend will not send canRename feature?

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.

3 participants