Skip to content

Conversation

DedSec256
Copy link
Collaborator

No description provided.

@DedSec256 DedSec256 force-pushed the net223-dedsec256-GetParametersGroups-api branch from d8cfae9 to 12ef383 Compare September 5, 2022 13:45
@auduchinok
Copy link
Member

@DedSec256 What's the state here?

@DedSec256
Copy link
Collaborator Author

@auduchinok, I'll try to finish it soon

@DedSec256 DedSec256 force-pushed the net223-dedsec256-GetParametersGroups-api branch from 12ef383 to 916adf4 Compare September 27, 2022 14:05
@auduchinok
Copy link
Member

@DedSec256 What do you think about splitting getting the parameter nodes and getting their names into separate APIs? Maybe something like this:

IReadOnlyList<IReadOnlyList<ITreeNode>> GetParameterNodes(ITreeNode node)
string GetParameterName(ITreeNode node)

The current API does two unrelated enough things and it doesn't seem right.

@auduchinok
Copy link
Member

A side note: we should try to build common interfaces that would remove this ITreeNode processing and use typed getters instead. That could be quite challenging due to different representations of parameters and may require us to change the tree structure, though.

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.

2 participants