ChimeraTK / ChimeraTK/ApplicationCore
VariableNetworkNode: inconsistent behaviour of getName() and getQualifiedName()
Open
Nobody has claimed this yet.
redmine
- Dominant language
- C++
- Stars
- 1
- Forks
- 5
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
VariableNetworkNode::getName() and VariableNetworkNode::getQualifiedName() return conceptionally different things depending on the type of the variable.
E.g. getName() gives for a variable "/mod/var":
- Application module: var
- Control system: /mod/var
And getQualifiedName() gives:
- Application module: /mod/var
- Control system: -> empty string
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate VariableNetworkNode and inspect getName() and getQualifiedName() along with their callers. Compare the application-module and control-system cases shown in the issue, then establish the intended consistent naming contract and verify both variable types behave accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100